Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65cf8d5073c374462851c85bbd4df6a07d00e3783362cdf5f1fdeecd71502732

Tx prefix hash: 3108dafe668556778f6f851b2dbac7f3745bc91741c865fe6e6fa111dc876748
Tx public key: d4bce9d1cd3a81318fc37924c3e121f2997aa49c68c73efecf044e253c66aafe
Timestamp: 1763209166 Timestamp [UCT]: 2025-11-15 12:19:26 Age [y:d:h:m:s]: 00:049:10:50:03
Block: 1412650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35423 RingCT/type: yes/0
Extra: 01d4bce9d1cd3a81318fc37924c3e121f2997aa49c68c73efecf044e253c66aafe0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 617dc9e38e9d7599def9e4f269b86c3da475a7e0f31998b91c642f41a88dfac0 0.600000000000 1901121 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": 1412660, "vin": [ { "gen": { "height": 1412650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "617dc9e38e9d7599def9e4f269b86c3da475a7e0f31998b91c642f41a88dfac0" } } ], "extra": [ 1, 212, 188, 233, 209, 205, 58, 129, 49, 143, 195, 121, 36, 195, 225, 33, 242, 153, 122, 164, 156, 104, 199, 62, 254, 207, 4, 78, 37, 60, 102, 170, 254, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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