Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a597b3c79ce4d2056aaf8c0c5f757a877507fc78b19e06b78644b83e96f565e2

Tx prefix hash: 0e9a723b1d142c849de316ce6304655944a0a639013abb6bbf27b3b691b44469
Tx public key: 6725a4a2aa08a3fa9c2d0f3a02e8bb3060f043468c2c9d66fa58490a122d8184
Timestamp: 1727015015 Timestamp [UCT]: 2024-09-22 14:23:35 Age [y:d:h:m:s]: 00:153:13:37:18
Block: 1115712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109533 RingCT/type: yes/0
Extra: 016725a4a2aa08a3fa9c2d0f3a02e8bb3060f043468c2c9d66fa58490a122d818402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 710cd9c96ead2513212b39fd4acfb59639272083960a48356dd8da0a90b852ba 0.600000000000 1595941 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": 1115722, "vin": [ { "gen": { "height": 1115712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "710cd9c96ead2513212b39fd4acfb59639272083960a48356dd8da0a90b852ba" } } ], "extra": [ 1, 103, 37, 164, 162, 170, 8, 163, 250, 156, 45, 15, 58, 2, 232, 187, 48, 96, 240, 67, 70, 140, 44, 157, 102, 250, 88, 73, 10, 18, 45, 129, 132, 2, 17, 0, 0, 0, 4, 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