Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1269986677b4e1e37fd2192a8e56fd0d7f4a92812f03d2cd42cfa5f3e3ead914

Tx prefix hash: 4cae739201707bc37ae353446bfef9c585d611d2d4199543371c63d96bfd366e
Tx public key: 5ab9970eb9a6f777c716262e30918b3c0bbbf9324ebeebcf19f58166cb805ce5
Timestamp: 1710471489 Timestamp [UCT]: 2024-03-15 02:58:09 Age [y:d:h:m:s]: 01:011:10:16:34
Block: 978579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269123 RingCT/type: yes/0
Extra: 015ab9970eb9a6f777c716262e30918b3c0bbbf9324ebeebcf19f58166cb805ce50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bb8dc5b21bc4fc05a46de1a0f5d6d6ba1fcc7dad5d210b5dd42211ea3765ab2 0.600000000000 1438606 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": 978589, "vin": [ { "gen": { "height": 978579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bb8dc5b21bc4fc05a46de1a0f5d6d6ba1fcc7dad5d210b5dd42211ea3765ab2" } } ], "extra": [ 1, 90, 185, 151, 14, 185, 166, 247, 119, 199, 22, 38, 46, 48, 145, 139, 60, 11, 187, 249, 50, 78, 190, 235, 207, 25, 245, 129, 102, 203, 128, 92, 229, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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