Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00ee55e62b02bfae47d6c7a05abe88e9e223d445e82895edadadb0b381c11dd8

Tx prefix hash: cacbed4b39f357120d8a5319071ea439a27cf38c37c721a4b0bb5e1a2c1218c7
Tx public key: 87ef208c38ba4b0a02c94fe8072ae57c32d8806cfebb93d03d603f32f59e4061
Timestamp: 1747695737 Timestamp [UCT]: 2025-05-19 23:02:17 Age [y:d:h:m:s]: 00:256:16:52:02
Block: 1286618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181104 RingCT/type: yes/0
Extra: 0187ef208c38ba4b0a02c94fe8072ae57c32d8806cfebb93d03d603f32f59e40610211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0809c063053ac0b38b3cc4b1bab3b2e8bd28f251abc7e7dc4e807a1312166ac1 0.600000000000 1774085 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": 1286628, "vin": [ { "gen": { "height": 1286618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0809c063053ac0b38b3cc4b1bab3b2e8bd28f251abc7e7dc4e807a1312166ac1" } } ], "extra": [ 1, 135, 239, 32, 140, 56, 186, 75, 10, 2, 201, 79, 232, 7, 42, 229, 124, 50, 216, 128, 108, 254, 187, 147, 208, 61, 96, 63, 50, 245, 158, 64, 97, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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