Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e7540e3dc467c8e4c7e841227b61dba45fab70895ca6dc316868d8b7335d48a

Tx prefix hash: d158da62b6c806f3d6ef887df3b9a2c1b29ce89c8004f3a0ab4c4c3bc6ca80a8
Tx public key: e5b6092a47219f3f8dcebf09910248d1c5db4a1c87f3d273ec0edcb9477a818e
Timestamp: 1710581217 Timestamp [UCT]: 2024-03-16 09:26:57 Age [y:d:h:m:s]: 01:020:00:33:40
Block: 979495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275269 RingCT/type: yes/0
Extra: 01e5b6092a47219f3f8dcebf09910248d1c5db4a1c87f3d273ec0edcb9477a818e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7d161738b1c3ba2d3f5bd8208560ce536e88ea477ba59f04c0ef2971f15dc36 0.600000000000 1439528 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": 979505, "vin": [ { "gen": { "height": 979495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7d161738b1c3ba2d3f5bd8208560ce536e88ea477ba59f04c0ef2971f15dc36" } } ], "extra": [ 1, 229, 182, 9, 42, 71, 33, 159, 63, 141, 206, 191, 9, 145, 2, 72, 209, 197, 219, 74, 28, 135, 243, 210, 115, 236, 14, 220, 185, 71, 122, 129, 142, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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