Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 655f4f8dd5eeefdc25e1e7f10d713c321fab2d5181fb46e04870cb1055e6dfdc

Tx prefix hash: c4f1c1377c39a53b59347f4c73e0d1a1aae3dab0d8d9cab87fb17af4997222e8
Tx public key: ccea8ac1a0198fdb81b9462ea29169308120fa7e879d60ad63e1ac973a043087
Timestamp: 1713266920 Timestamp [UCT]: 2024-04-16 11:28:40 Age [y:d:h:m:s]: 00:351:07:43:55
Block: 1001716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251174 RingCT/type: yes/0
Extra: 01ccea8ac1a0198fdb81b9462ea29169308120fa7e879d60ad63e1ac973a04308702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fff6c88f30169bdb2fae0a734ab9f01fb64955cc074b775b37b88325a997183 0.600000000000 1462224 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": 1001726, "vin": [ { "gen": { "height": 1001716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fff6c88f30169bdb2fae0a734ab9f01fb64955cc074b775b37b88325a997183" } } ], "extra": [ 1, 204, 234, 138, 193, 160, 25, 143, 219, 129, 185, 70, 46, 162, 145, 105, 48, 129, 32, 250, 126, 135, 157, 96, 173, 99, 225, 172, 151, 58, 4, 48, 135, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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