Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a4cee780af5b35e55177df3a61df675905c21c47910e7ac6c660fa04705d97

Tx prefix hash: b9ba8c696f80db977ef33b8bd40a297f2ba5068489df2c522e9c960d12dd7cdd
Tx public key: bf4bca75a7ab9754e18b01d32392ee47e91ef5c72ceefb84c9cc4ee09b2e9e81
Timestamp: 1735161576 Timestamp [UCT]: 2024-12-25 21:19:36 Age [y:d:h:m:s]: 00:089:19:13:38
Block: 1183137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63950 RingCT/type: yes/0
Extra: 01bf4bca75a7ab9754e18b01d32392ee47e91ef5c72ceefb84c9cc4ee09b2e9e81021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42ca1663f62fc9f616139cce580f4feb3cb91dcddbf2b900b7809c07a58712f6 0.600000000000 1669578 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": 1183147, "vin": [ { "gen": { "height": 1183137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42ca1663f62fc9f616139cce580f4feb3cb91dcddbf2b900b7809c07a58712f6" } } ], "extra": [ 1, 191, 75, 202, 117, 167, 171, 151, 84, 225, 139, 1, 211, 35, 146, 238, 71, 233, 30, 245, 199, 44, 238, 251, 132, 201, 204, 78, 224, 155, 46, 158, 129, 2, 17, 0, 0, 0, 5, 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