Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06a64172bbbb11015cc53c049084f3ffb2709e3c8576994f1a734406b10cad39

Tx prefix hash: 6a06e590d7e96e54126560e6643fa7b2ddf2f9d8f2991d9c8fa91954c0e36e7b
Tx public key: 389d9fa8c5768c9d9afbc86f151ac2fb1b91ab413d29b1dfe47ae0df431d70d3
Timestamp: 1719848155 Timestamp [UCT]: 2024-07-01 15:35:55 Age [y:d:h:m:s]: 00:282:16:52:19
Block: 1056293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202001 RingCT/type: yes/0
Extra: 01389d9fa8c5768c9d9afbc86f151ac2fb1b91ab413d29b1dfe47ae0df431d70d30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8226ac25673425d529d8e54c3312d3c5f4411d065848b8eff1ae9d22977372cf 0.600000000000 1526706 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": 1056303, "vin": [ { "gen": { "height": 1056293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8226ac25673425d529d8e54c3312d3c5f4411d065848b8eff1ae9d22977372cf" } } ], "extra": [ 1, 56, 157, 159, 168, 197, 118, 140, 157, 154, 251, 200, 111, 21, 26, 194, 251, 27, 145, 171, 65, 61, 41, 177, 223, 228, 122, 224, 223, 67, 29, 112, 211, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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