Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc750a1fed5c7be1df8b2545bcb9390fd11a71a5821780fa8cd5091538348579

Tx prefix hash: 51d1b7547b4bf78d5b2beb5823a82ebcac9203069be7f118d0d5f656e6954a94
Tx public key: c1e83f1bbc224bf58d6ac8a75ddcf603630590bf197c526b384c1703d42e3e8e
Timestamp: 1729749383 Timestamp [UCT]: 2024-10-24 05:56:23 Age [y:d:h:m:s]: 01:018:09:07:01
Block: 1138356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271514 RingCT/type: yes/0
Extra: 01c1e83f1bbc224bf58d6ac8a75ddcf603630590bf197c526b384c1703d42e3e8e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0a905dcbe9c244ca0f50662b23a5a7da1f7443671a9b41ca491000ccf8327a7 0.600000000000 1621999 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": 1138366, "vin": [ { "gen": { "height": 1138356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0a905dcbe9c244ca0f50662b23a5a7da1f7443671a9b41ca491000ccf8327a7" } } ], "extra": [ 1, 193, 232, 63, 27, 188, 34, 75, 245, 141, 106, 200, 167, 93, 220, 246, 3, 99, 5, 144, 191, 25, 124, 82, 107, 56, 76, 23, 3, 212, 46, 62, 142, 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