Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2255d68d9643469d066de003fde7c30314fde3ad443a4885d8b649e3113c2b73

Tx prefix hash: a6c1acf40e5a73958a0ed9c636058c84f0d9670cd94509325603e636044eae49
Tx public key: f90717c3c3dbdaf13178b366ea98b1702b21ded43a844f2ead05dc821a0cbe39
Timestamp: 1737779443 Timestamp [UCT]: 2025-01-25 04:30:43 Age [y:d:h:m:s]: 00:143:13:45:41
Block: 1204760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102353 RingCT/type: yes/0
Extra: 01f90717c3c3dbdaf13178b366ea98b1702b21ded43a844f2ead05dc821a0cbe390211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae317e6f5d2ef3b06dcae3938437850bb28edae84e2aef7b1e5c5f9f58456c67 0.600000000000 1691453 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": 1204770, "vin": [ { "gen": { "height": 1204760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae317e6f5d2ef3b06dcae3938437850bb28edae84e2aef7b1e5c5f9f58456c67" } } ], "extra": [ 1, 249, 7, 23, 195, 195, 219, 218, 241, 49, 120, 179, 102, 234, 152, 177, 112, 43, 33, 222, 212, 58, 132, 79, 46, 173, 5, 220, 130, 26, 12, 190, 57, 2, 17, 0, 0, 0, 3, 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