Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55db19989f3beaed34fba4a8aaea42a64fec0ed852b6a4c0244416ad6d371c78

Tx prefix hash: 43dfb50bf288de91de0742aad5282de0add19861f6c9ff7a0b084b687927c071
Tx public key: 11eae0280ed223fa5e1ac0c4bf2c00724a49b33cea75a4084c7199572fd021cd
Timestamp: 1737365907 Timestamp [UCT]: 2025-01-20 09:38:27 Age [y:d:h:m:s]: 00:149:14:04:22
Block: 1201330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106644 RingCT/type: yes/0
Extra: 0111eae0280ed223fa5e1ac0c4bf2c00724a49b33cea75a4084c7199572fd021cd0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73f8933c0f2b77c3c3f0bca8db0ee009d24b83e8c77ac56c7bbc6e7fb439c529 0.600000000000 1687979 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": 1201340, "vin": [ { "gen": { "height": 1201330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73f8933c0f2b77c3c3f0bca8db0ee009d24b83e8c77ac56c7bbc6e7fb439c529" } } ], "extra": [ 1, 17, 234, 224, 40, 14, 210, 35, 250, 94, 26, 192, 196, 191, 44, 0, 114, 74, 73, 179, 60, 234, 117, 164, 8, 76, 113, 153, 87, 47, 208, 33, 205, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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