Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b05362692edf461d14e6a58866cab6cbf73b6c91378a2a391e32d5ecfbcff46f

Tx prefix hash: bc6df98b9fbb2b61cc9a7b72a7c096ccb8b92c58418dec5d3ce116f994829d0a
Tx public key: 7ac1ddab24daabac5e26efed96baa6c72961aa810f69dd7ea0534dba87ce3da3
Timestamp: 1721138355 Timestamp [UCT]: 2024-07-16 13:59:15 Age [y:d:h:m:s]: 00:265:17:43:23
Block: 1067008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189825 RingCT/type: yes/0
Extra: 017ac1ddab24daabac5e26efed96baa6c72961aa810f69dd7ea0534dba87ce3da302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63c4cdbec05796be76710c4c525da93c556861bc828b91c6e6e7d1efcd54101e 0.600000000000 1537705 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": 1067018, "vin": [ { "gen": { "height": 1067008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63c4cdbec05796be76710c4c525da93c556861bc828b91c6e6e7d1efcd54101e" } } ], "extra": [ 1, 122, 193, 221, 171, 36, 218, 171, 172, 94, 38, 239, 237, 150, 186, 166, 199, 41, 97, 170, 129, 15, 105, 221, 126, 160, 83, 77, 186, 135, 206, 61, 163, 2, 17, 0, 0, 0, 3, 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