Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a9708fd2119f05f90e4ccffac6c99d5b93c9b454f6769033f85be84512465c0

Tx prefix hash: 2fb1c7f4a47a572ab81089988ffd423b0583e510c04e1786d2751c561533fc01
Tx public key: 76efecd5f0f94fc954a6e5365a7e913ed80fcb9d749e5a0e10826765ec89f138
Timestamp: 1715727074 Timestamp [UCT]: 2024-05-14 22:51:14 Age [y:d:h:m:s]: 00:337:05:05:21
Block: 1022137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241027 RingCT/type: yes/0
Extra: 0176efecd5f0f94fc954a6e5365a7e913ed80fcb9d749e5a0e10826765ec89f13802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a32dce91dd30575b826e9b5d3a9594f910bd4e86dc62d046cd74673debcee91c 0.600000000000 1486650 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": 1022147, "vin": [ { "gen": { "height": 1022137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a32dce91dd30575b826e9b5d3a9594f910bd4e86dc62d046cd74673debcee91c" } } ], "extra": [ 1, 118, 239, 236, 213, 240, 249, 79, 201, 84, 166, 229, 54, 90, 126, 145, 62, 216, 15, 203, 157, 116, 158, 90, 14, 16, 130, 103, 101, 236, 137, 241, 56, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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