Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f642a1a49514bd05a033bd1f3a71041e3ea5bb1f4df4728a2a5089f2e01cbdc1

Tx prefix hash: 8779b79a19436d0a44d89966b3a0e497d6eac5645bd498a4545379722a65cfa3
Tx public key: ca84a60efac950544b381dfe0eaa613f03f8b8f8ef391b5b9495a6a805a07333
Timestamp: 1765683935 Timestamp [UCT]: 2025-12-14 03:45:35 Age [y:d:h:m:s]: 00:020:09:05:51
Block: 1433152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14606 RingCT/type: yes/0
Extra: 01ca84a60efac950544b381dfe0eaa613f03f8b8f8ef391b5b9495a6a805a07333021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354bf98ada21bcbe510520d66af2da9b63430e720bf8dd19212aa16d8d301362 0.600000000000 1921931 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": 1433162, "vin": [ { "gen": { "height": 1433152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354bf98ada21bcbe510520d66af2da9b63430e720bf8dd19212aa16d8d301362" } } ], "extra": [ 1, 202, 132, 166, 14, 250, 201, 80, 84, 75, 56, 29, 254, 14, 170, 97, 63, 3, 248, 184, 248, 239, 57, 27, 91, 148, 149, 166, 168, 5, 160, 115, 51, 2, 17, 0, 0, 0, 8, 214, 225, 157, 124, 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