Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 008cb3550b6b6c5a5dacbe8a9e203e33965627b16141fffd11f23c0885563f49

Tx prefix hash: 9d7148d579880d20a25bd0d159da78531f797f5ff2d1aeb54890b596c001a49b
Tx public key: c50e543f97c15f77d2fb21731783cf69a7ba19d56d099e75f75cceac20b6f4c5
Timestamp: 1704138910 Timestamp [UCT]: 2024-01-01 19:55:10 Age [y:d:h:m:s]: 01:093:05:06:48
Block: 926055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327729 RingCT/type: yes/0
Extra: 01c50e543f97c15f77d2fb21731783cf69a7ba19d56d099e75f75cceac20b6f4c502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14b69b91d8d9db334eae886209d4ba9510ba3574fc3aef22ecae691f1d72161c 0.600000000000 1383829 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": 926065, "vin": [ { "gen": { "height": 926055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14b69b91d8d9db334eae886209d4ba9510ba3574fc3aef22ecae691f1d72161c" } } ], "extra": [ 1, 197, 14, 84, 63, 151, 193, 95, 119, 210, 251, 33, 115, 23, 131, 207, 105, 167, 186, 25, 213, 109, 9, 158, 117, 247, 92, 206, 172, 32, 182, 244, 197, 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