Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea05284f0af4e62215664320abebf9c36f815f6d66fdab4084614a6efc3431a

Tx prefix hash: 95bcc3bc4c8ae03ad8cbdaacf081f04f9b78afda146a392777986863f5f843e5
Tx public key: 70603690ec2feade8556e4f3fdb0d31f4c9366b1a3a43e9e95d180f2838dadf1
Timestamp: 1751520438 Timestamp [UCT]: 2025-07-03 05:27:18 Age [y:d:h:m:s]: 00:132:15:37:55
Block: 1317724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93040 RingCT/type: yes/0
Extra: 0170603690ec2feade8556e4f3fdb0d31f4c9366b1a3a43e9e95d180f2838dadf1021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd54f6c828aea835efb517b8549ab3a89987a5827acc46237f43aac9eebf471c 0.600000000000 1805393 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": 1317734, "vin": [ { "gen": { "height": 1317724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd54f6c828aea835efb517b8549ab3a89987a5827acc46237f43aac9eebf471c" } } ], "extra": [ 1, 112, 96, 54, 144, 236, 47, 234, 222, 133, 86, 228, 243, 253, 176, 211, 31, 76, 147, 102, 177, 163, 164, 62, 158, 149, 209, 128, 242, 131, 141, 173, 241, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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