Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d41d2474d8260f58ee06cbdfbeda7a1c4215aa8a641f3336237bf64a28b294bd

Tx prefix hash: 69cd24c4d4de71c7698c2d70b95f01ec4ecaebbba8c7d101471da75496c5804c
Tx public key: 8257fc0e2ff7556681f23eb03b3c3c108867593c8b5644a8ac0c211ce1f2bbd1
Timestamp: 1712810485 Timestamp [UCT]: 2024-04-11 04:41:25 Age [y:d:h:m:s]: 00:342:17:34:36
Block: 997928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245069 RingCT/type: yes/0
Extra: 018257fc0e2ff7556681f23eb03b3c3c108867593c8b5644a8ac0c211ce1f2bbd102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 229b308c1d3622f5fe4e0b9b37b6507c53318ee75ca741e20d4e37cd67ac3280 0.600000000000 1458362 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": 997938, "vin": [ { "gen": { "height": 997928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "229b308c1d3622f5fe4e0b9b37b6507c53318ee75ca741e20d4e37cd67ac3280" } } ], "extra": [ 1, 130, 87, 252, 14, 47, 247, 85, 102, 129, 242, 62, 176, 59, 60, 60, 16, 136, 103, 89, 60, 139, 86, 68, 168, 172, 12, 33, 28, 225, 242, 187, 209, 2, 17, 0, 0, 0, 5, 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