Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a20872b4d2d8fa103f07fbd75cddf822aa707edd5e270ffb1c1d6684e74ae631

Tx prefix hash: e0d1591e38cf8c8bc352d90d5394fc0560caccaaa2ef50eb3827ebd88d9fd80c
Tx public key: 4b019c541c52791626d6d586e63f32efcf875484d8d32cd9964150a01b29eab7
Timestamp: 1725166258 Timestamp [UCT]: 2024-09-01 04:50:58 Age [y:d:h:m:s]: 00:219:16:08:14
Block: 1100384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156847 RingCT/type: yes/0
Extra: 014b019c541c52791626d6d586e63f32efcf875484d8d32cd9964150a01b29eab702110000000391e13c04000000000000000000

1 output(s) for total of 0.600090000000 dcy

stealth address amount amount idx
00: 2e648921be5b3eafc66b96a32ff11ae170eef3fa30c2ad9f60dd9883c134b7e4 0.600090000000 1576361 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": 1100394, "vin": [ { "gen": { "height": 1100384 } } ], "vout": [ { "amount": 600090000, "target": { "key": "2e648921be5b3eafc66b96a32ff11ae170eef3fa30c2ad9f60dd9883c134b7e4" } } ], "extra": [ 1, 75, 1, 156, 84, 28, 82, 121, 22, 38, 214, 213, 134, 230, 63, 50, 239, 207, 135, 84, 132, 216, 211, 44, 217, 150, 65, 80, 160, 27, 41, 234, 183, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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