Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b95ba4c309f05332e51d10f78316188b98cd0496435e5e71cff6823e3270f7b

Tx prefix hash: 397e238e7caf64402c247cac100f2f000df54801a47fba2169162c7fa3e2009f
Tx public key: bde3b957dc91e08da3303c3806bfe06d017e75cc3a366ab7f054ca026bd1b92e
Timestamp: 1705566746 Timestamp [UCT]: 2024-01-18 08:32:26 Age [y:d:h:m:s]: 00:296:15:05:43
Block: 937880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212412 RingCT/type: yes/0
Extra: 01bde3b957dc91e08da3303c3806bfe06d017e75cc3a366ab7f054ca026bd1b92e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c8a10e24d8c8c02569da7ad1f9241371b9c043fd4ce25470d07ab55bcbe25dc 0.600000000000 1395944 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": 937890, "vin": [ { "gen": { "height": 937880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c8a10e24d8c8c02569da7ad1f9241371b9c043fd4ce25470d07ab55bcbe25dc" } } ], "extra": [ 1, 189, 227, 185, 87, 220, 145, 224, 141, 163, 48, 60, 56, 6, 191, 224, 109, 1, 126, 117, 204, 58, 54, 106, 183, 240, 84, 202, 2, 107, 209, 185, 46, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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