Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2acb41950ada44d172c31c35b679157cf7196802f24fd541b3efa756bbba1f0

Tx prefix hash: 3dac4babae7bb026094b2b5928a59923748f8bbd2183aa7c6654520d3eb19652
Tx public key: 9937dc9163d1fd8b3b523d8d2f3ca64d78525f0c73bee7262dddc414419ce4ec
Timestamp: 1733305348 Timestamp [UCT]: 2024-12-04 09:42:28 Age [y:d:h:m:s]: 00:101:05:04:35
Block: 1167760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72149 RingCT/type: yes/0
Extra: 019937dc9163d1fd8b3b523d8d2f3ca64d78525f0c73bee7262dddc414419ce4ec0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428d71a8b224c7e48f21efbe9933f8843f77969cf46bb4cac1cf2b81923921f7 0.600000000000 1653463 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": 1167770, "vin": [ { "gen": { "height": 1167760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428d71a8b224c7e48f21efbe9933f8843f77969cf46bb4cac1cf2b81923921f7" } } ], "extra": [ 1, 153, 55, 220, 145, 99, 209, 253, 139, 59, 82, 61, 141, 47, 60, 166, 77, 120, 82, 95, 12, 115, 190, 231, 38, 45, 221, 196, 20, 65, 156, 228, 236, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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