Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8439c4c2e749371773825c356908c66652d7ca17fc6c10a88d1bab13a7cde9e6

Tx prefix hash: b58fc69deb35474c004cdd0d3ab4a43cae457cacbd2f5eb7c11bb451892ac7e7
Tx public key: b18162c92f8a9cc0514d40b90ae5adad879ea508c133b6a4bb9aca10aa5915a0
Timestamp: 1748578179 Timestamp [UCT]: 2025-05-30 04:09:39 Age [y:d:h:m:s]: 00:175:19:54:05
Block: 1293944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123352 RingCT/type: yes/0
Extra: 01b18162c92f8a9cc0514d40b90ae5adad879ea508c133b6a4bb9aca10aa5915a0021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd4c2aaba9444ef8dffd4fdc47fa26a0c732766f2cc2427cfc995144aa60403 0.600000000000 1781439 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": 1293954, "vin": [ { "gen": { "height": 1293944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd4c2aaba9444ef8dffd4fdc47fa26a0c732766f2cc2427cfc995144aa60403" } } ], "extra": [ 1, 177, 129, 98, 201, 47, 138, 156, 192, 81, 77, 64, 185, 10, 229, 173, 173, 135, 158, 165, 8, 193, 51, 182, 164, 187, 154, 202, 16, 170, 89, 21, 160, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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