Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8de94a85b6490dd8a965d0202406b332750d8301925d64359df2ffc213c2923a

Tx prefix hash: f050310f712452a5826f4222f7daecb7a8cbea8cfdd812d331bdf697a3ea1de5
Tx public key: d9e76c4647997aaaa4b3f51b95b2d4e2608d4cead059c088cd676e39f3d8e224
Timestamp: 1766266537 Timestamp [UCT]: 2025-12-20 21:35:37 Age [y:d:h:m:s]: 00:001:06:38:34
Block: 1437999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 902 RingCT/type: yes/0
Extra: 01d9e76c4647997aaaa4b3f51b95b2d4e2608d4cead059c088cd676e39f3d8e22402110000000c7b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d6784067c0a4349ead6641720526cde82daf26ca5d6869a1239bcdddb8a3b2a 0.600000000000 1926814 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": 1438009, "vin": [ { "gen": { "height": 1437999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d6784067c0a4349ead6641720526cde82daf26ca5d6869a1239bcdddb8a3b2a" } } ], "extra": [ 1, 217, 231, 108, 70, 71, 153, 122, 170, 164, 179, 245, 27, 149, 178, 212, 226, 96, 141, 76, 234, 208, 89, 192, 136, 205, 103, 110, 57, 243, 216, 226, 36, 2, 17, 0, 0, 0, 12, 123, 30, 81, 172, 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