Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60452804278e59d5acd8b0d64b4f4dcc458d45c04b5cd9261755db3ba627cb83

Tx prefix hash: eef27c7d09dc51f2eb2ef9ca2e571f916dcd25b6ac721fdca75c10adaf6631fd
Tx public key: b1ebded37ef78afd821ace5df1972624f8805a3cfed63b2f51e0677d574a008a
Timestamp: 1728193793 Timestamp [UCT]: 2024-10-06 05:49:53 Age [y:d:h:m:s]: 00:204:08:40:37
Block: 1125485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145877 RingCT/type: yes/0
Extra: 01b1ebded37ef78afd821ace5df1972624f8805a3cfed63b2f51e0677d574a008a02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b4b49fa34e99b7e9d62c625a24196e83c1bf883e1802a06acf15bc23f73f646 0.600000000000 1608236 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": 1125495, "vin": [ { "gen": { "height": 1125485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b4b49fa34e99b7e9d62c625a24196e83c1bf883e1802a06acf15bc23f73f646" } } ], "extra": [ 1, 177, 235, 222, 211, 126, 247, 138, 253, 130, 26, 206, 93, 241, 151, 38, 36, 248, 128, 90, 60, 254, 214, 59, 47, 81, 224, 103, 125, 87, 74, 0, 138, 2, 17, 0, 0, 0, 14, 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