Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64add4c9f81f545bd43ed2e85af131543ea1a5c665f5120ec11cc0c49946acc

Tx prefix hash: 96777b5f934f6da8e64d59bf8081f9ec41ca0bbc83f1444d816b1052db1f0493
Tx public key: d4de756c060926bd979c1ef3c8c58bfc1e54116a0240c09e1d879521b95c4e7d
Timestamp: 1753977848 Timestamp [UCT]: 2025-07-31 16:04:08 Age [y:d:h:m:s]: 00:023:03:33:18
Block: 1337430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15474 RingCT/type: yes/0
Extra: 01d4de756c060926bd979c1ef3c8c58bfc1e54116a0240c09e1d879521b95c4e7d021100000009ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c012ce555647a010212986e0b8f27b6ca619af072893c1f57d9ba6158fcf8858 0.600000000000 1825235 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": 1337440, "vin": [ { "gen": { "height": 1337430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c012ce555647a010212986e0b8f27b6ca619af072893c1f57d9ba6158fcf8858" } } ], "extra": [ 1, 212, 222, 117, 108, 6, 9, 38, 189, 151, 156, 30, 243, 200, 197, 139, 252, 30, 84, 17, 106, 2, 64, 192, 158, 29, 135, 149, 33, 185, 92, 78, 125, 2, 17, 0, 0, 0, 9, 173, 121, 72, 208, 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