Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9d4d797d062cbc14e188910d89d19158d97c64ed5105b72b9cd00937691d194

Tx prefix hash: 681083f68cba3bad5c2264ac4b8dff6ef4ec30e406a85d2a7dfb53896c6cd5f2
Tx public key: e6d0141b73ee41627a73fe5f54fd0dd4463afc49a1fa439539b1c6430de310a5
Timestamp: 1746019934 Timestamp [UCT]: 2025-04-30 13:32:14 Age [y:d:h:m:s]: 00:203:18:29:15
Block: 1272752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143355 RingCT/type: yes/0
Extra: 01e6d0141b73ee41627a73fe5f54fd0dd4463afc49a1fa439539b1c6430de310a502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70894e3094620ca5cb124d5074c9e03e632c213caeb806f7083f9d14ed96857e 0.600000000000 1760027 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": 1272762, "vin": [ { "gen": { "height": 1272752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70894e3094620ca5cb124d5074c9e03e632c213caeb806f7083f9d14ed96857e" } } ], "extra": [ 1, 230, 208, 20, 27, 115, 238, 65, 98, 122, 115, 254, 95, 84, 253, 13, 212, 70, 58, 252, 73, 161, 250, 67, 149, 57, 177, 198, 67, 13, 227, 16, 165, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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