Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f664270b4121ea00627ecf79319827732ea8b2c3cf7861bb69b5da8fc1e30a6

Tx prefix hash: 0c8da1f76e2e50782ed40f7c1e537c3170381213ed0b48fbd9533d1f9b9f9e02
Tx public key: e5f63a9cc7a36aa8fa25d65ec892b7f5b55eb6c5e56fa78b0ab2f47a5cc9fbb1
Timestamp: 1713877528 Timestamp [UCT]: 2024-04-23 13:05:28 Age [y:d:h:m:s]: 01:196:15:14:14
Block: 1006801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399150 RingCT/type: yes/0
Extra: 01e5f63a9cc7a36aa8fa25d65ec892b7f5b55eb6c5e56fa78b0ab2f47a5cc9fbb10211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ae0d759089c6968ce80f88a263a8b7b412f5ee80b148136652c9a41b3418885 0.600000000000 1467941 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": 1006811, "vin": [ { "gen": { "height": 1006801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ae0d759089c6968ce80f88a263a8b7b412f5ee80b148136652c9a41b3418885" } } ], "extra": [ 1, 229, 246, 58, 156, 199, 163, 106, 168, 250, 37, 214, 94, 200, 146, 183, 245, 181, 94, 182, 197, 229, 111, 167, 139, 10, 178, 244, 122, 92, 201, 251, 177, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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