Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03371d024f3961ceedc0c0d6974ae1b41af6ec8b243be2dbeeec666321ff8b6b

Tx prefix hash: 5f6ef3459bc3313bd49687fa623a2e9b79ae2712756ba14e7f01aa710480b585
Tx public key: c8a311c2b77a4a358dcb80ed5bc947d1093d9f164f81193b3b13fec3bc3a8e0a
Timestamp: 1714025458 Timestamp [UCT]: 2024-04-25 06:10:58 Age [y:d:h:m:s]: 01:189:13:08:30
Block: 1008015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394118 RingCT/type: yes/0
Extra: 01c8a311c2b77a4a358dcb80ed5bc947d1093d9f164f81193b3b13fec3bc3a8e0a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 396f7fb7a8f8c9c6d21cac8a0d57ecae099167f9cb5ce48b754b9e0caca65199 0.600000000000 1469481 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": 1008025, "vin": [ { "gen": { "height": 1008015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "396f7fb7a8f8c9c6d21cac8a0d57ecae099167f9cb5ce48b754b9e0caca65199" } } ], "extra": [ 1, 200, 163, 17, 194, 183, 122, 74, 53, 141, 203, 128, 237, 91, 201, 71, 209, 9, 61, 159, 22, 79, 129, 25, 59, 59, 19, 254, 195, 188, 58, 142, 10, 2, 17, 0, 0, 0, 1, 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