Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5cae0c6e56488f3dd659bfbd1c9d7587737a22aa71a69aff6ea2ccb73f6f3c6

Tx prefix hash: b685114756225d46329409020493f17b06d532807246f20150856613b6b7d527
Tx public key: e8a2fa5df9d90ad0c8e1805f011d3e95ee81ca640282c94e710c715118454f1a
Timestamp: 1736082828 Timestamp [UCT]: 2025-01-05 13:13:48 Age [y:d:h:m:s]: 00:099:02:06:32
Block: 1190764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70601 RingCT/type: yes/0
Extra: 01e8a2fa5df9d90ad0c8e1805f011d3e95ee81ca640282c94e710c715118454f1a02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc4ba4fc0834f12d25b58a77571d65119cc8f886a554751d687e429e0acf61e1 0.600000000000 1677283 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": 1190774, "vin": [ { "gen": { "height": 1190764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc4ba4fc0834f12d25b58a77571d65119cc8f886a554751d687e429e0acf61e1" } } ], "extra": [ 1, 232, 162, 250, 93, 249, 217, 10, 208, 200, 225, 128, 95, 1, 29, 62, 149, 238, 129, 202, 100, 2, 130, 201, 78, 113, 12, 113, 81, 24, 69, 79, 26, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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