Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef68679cc9638d5538e2c2c37470d35846f3c3e8e7e2f53d9144c725d9d5d5a1

Tx prefix hash: ba4e3399f48627a5977bdb99ba3454d3d87251d2ced036f2b1abade3c710bf8f
Tx public key: 9ebf244dc360938ebe4d866cebbaa4dcd9bd8ed1b05e4b75433339930f99e738
Timestamp: 1734592651 Timestamp [UCT]: 2024-12-19 07:17:31 Age [y:d:h:m:s]: 00:324:19:32:12
Block: 1178445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229627 RingCT/type: yes/0
Extra: 019ebf244dc360938ebe4d866cebbaa4dcd9bd8ed1b05e4b75433339930f99e738021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3244a43013e557304f619a73a0cb640a169447583a42d40c86b4f52d8f6afd53 0.600000000000 1664832 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": 1178455, "vin": [ { "gen": { "height": 1178445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3244a43013e557304f619a73a0cb640a169447583a42d40c86b4f52d8f6afd53" } } ], "extra": [ 1, 158, 191, 36, 77, 195, 96, 147, 142, 190, 77, 134, 108, 235, 186, 164, 220, 217, 189, 142, 209, 176, 94, 75, 117, 67, 51, 57, 147, 15, 153, 231, 56, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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