Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2bda5b9ccb3c337e736c47ff5349f7ecf45e0a295ae457aa06983ce74a0d90eb

Tx prefix hash: 206881f7fa5c5b980a75efa232d58091e9c4f73aad630eaa5502068885bcfa3d
Tx public key: ff020ef5a06ef9a31f8392304b5b4573cf259bea32aa7254cf752f4996320077
Timestamp: 1708716402 Timestamp [UCT]: 2024-02-23 19:26:42 Age [y:d:h:m:s]: 01:271:19:13:54
Block: 964006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453007 RingCT/type: yes/0
Extra: 01ff020ef5a06ef9a31f8392304b5b4573cf259bea32aa7254cf752f49963200770211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cd2fd9b56e3ec927a8a0c71cba2a0d949be44790f4d93b72c0d5555ee56c0f4 0.600000000000 1423733 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 964016, "vin": [ { "gen": { "height": 964006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cd2fd9b56e3ec927a8a0c71cba2a0d949be44790f4d93b72c0d5555ee56c0f4" } } ], "extra": [ 1, 255, 2, 14, 245, 160, 110, 249, 163, 31, 131, 146, 48, 75, 91, 69, 115, 207, 37, 155, 234, 50, 170, 114, 84, 207, 117, 47, 73, 150, 50, 0, 119, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8