Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a900ae0b17b01d409878ee275316c91a59fa863efe075c3d151333ecb7dbd0e0

Tx prefix hash: bc67a00940554d0d2a4c31cb95bcb58796b2cd3c3feafd650b299df2b9d78da3
Tx public key: df912e812a99aa996358cc642df50fa543fbcb5249c95fa2e6d3c651fc5aebc1
Timestamp: 1735992167 Timestamp [UCT]: 2025-01-04 12:02:47 Age [y:d:h:m:s]: 00:129:14:43:15
Block: 1190007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92439 RingCT/type: yes/0
Extra: 01df912e812a99aa996358cc642df50fa543fbcb5249c95fa2e6d3c651fc5aebc10211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 689155febd2b762d1aa17ba11f0ec5517434b4c2f9a21ea977d29f174edbded9 0.600000000000 1676522 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": 1190017, "vin": [ { "gen": { "height": 1190007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "689155febd2b762d1aa17ba11f0ec5517434b4c2f9a21ea977d29f174edbded9" } } ], "extra": [ 1, 223, 145, 46, 129, 42, 153, 170, 153, 99, 88, 204, 100, 45, 245, 15, 165, 67, 251, 203, 82, 73, 201, 95, 162, 230, 211, 198, 81, 252, 90, 235, 193, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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