Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 477817e8f1280fe8991b6cd051c8a98d5eaa74df4e51d4d8ab1c623ac250b9a6

Tx prefix hash: 64eea3d4c43914e0e0c9dcec440e319f693abfd71c72a3997e24dd6e37d07516
Tx public key: 807736f308e17d410d518bc0490864484e2fef9bdac3fc005fc602867fbe35b6
Timestamp: 1731606361 Timestamp [UCT]: 2024-11-14 17:46:01 Age [y:d:h:m:s]: 00:217:10:45:23
Block: 1153691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155135 RingCT/type: yes/0
Extra: 01807736f308e17d410d518bc0490864484e2fef9bdac3fc005fc602867fbe35b6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5738116055eb2811ca0f8688f90ff7bed9cf0edd0fd54693ae7dc359209ea02c 0.600000000000 1639302 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": 1153701, "vin": [ { "gen": { "height": 1153691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5738116055eb2811ca0f8688f90ff7bed9cf0edd0fd54693ae7dc359209ea02c" } } ], "extra": [ 1, 128, 119, 54, 243, 8, 225, 125, 65, 13, 81, 139, 192, 73, 8, 100, 72, 78, 47, 239, 155, 218, 195, 252, 0, 95, 198, 2, 134, 127, 190, 53, 182, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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