Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c444511104f770bdeec71c551e1c3bfd71ff511b9baa41e4fdb8d452445c4527

Tx prefix hash: b495d3ff399b3c9116056c2a8c675ff9d668df41ea40f9fa8d2e8bbefc701002
Tx public key: 8cf2a7812403e793ebc5e4372d0cf5c33e5b3b9173e65457a5ac25792fd9ee30
Timestamp: 1715603373 Timestamp [UCT]: 2024-05-13 12:29:33 Age [y:d:h:m:s]: 00:323:23:33:03
Block: 1021132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231548 RingCT/type: yes/0
Extra: 018cf2a7812403e793ebc5e4372d0cf5c33e5b3b9173e65457a5ac25792fd9ee300211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f54214a846ce256f195a321075540372a5708a3bd0304b43eeb45cb501b6ae9e 0.600000000000 1485349 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": 1021142, "vin": [ { "gen": { "height": 1021132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f54214a846ce256f195a321075540372a5708a3bd0304b43eeb45cb501b6ae9e" } } ], "extra": [ 1, 140, 242, 167, 129, 36, 3, 231, 147, 235, 197, 228, 55, 45, 12, 245, 195, 62, 91, 59, 145, 115, 230, 84, 87, 165, 172, 37, 121, 47, 217, 238, 48, 2, 17, 0, 0, 0, 5, 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