Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 660e6b583f4e3be2b75c6ebfb6cd2420beeb966586114f9951a2f75024c6e034

Tx prefix hash: d571bcc2f72f54ff997170145112a5d79d923c8a9315f54c906af6d7dc3cdaeb
Tx public key: 6a975ae4f3b3d1790dba1e083e7eaf7f09afd2ed3503b9101b5bdca97cb3b1c7
Timestamp: 1638732624 Timestamp [UCT]: 2021-12-05 19:30:24 Age [y:d:h:m:s]: 03:099:17:03:38
Block: 389145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 849986 RingCT/type: yes/0
Extra: 016a975ae4f3b3d1790dba1e083e7eaf7f09afd2ed3503b9101b5bdca97cb3b1c702110000000138be87f4000000000000000000

1 output(s) for total of 31.521105501000 dcy

stealth address amount amount idx
00: 53e58767dcad3ba40e508a7cb37b4967e0a72fe147b553f49b0be1e4cb330444 31.521105501000 784172 of 0

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": 389155, "vin": [ { "gen": { "height": 389145 } } ], "vout": [ { "amount": 31521105501, "target": { "key": "53e58767dcad3ba40e508a7cb37b4967e0a72fe147b553f49b0be1e4cb330444" } } ], "extra": [ 1, 106, 151, 90, 228, 243, 179, 209, 121, 13, 186, 30, 8, 62, 126, 175, 127, 9, 175, 210, 237, 53, 3, 185, 16, 27, 91, 220, 169, 124, 179, 177, 199, 2, 17, 0, 0, 0, 1, 56, 190, 135, 244, 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