Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0411f4d952ca3a725c293b19a3f7fbe5e6f85fcd849b1163688c34a90ba8744d

Tx prefix hash: 84206c159e74db878fd8b4bf61e7be0b95cfc187f82541321d347590a3ac5e06
Tx public key: 1cdf32fdcccc68b9f46d20050c7497ec0d45a11d17f85a86384087d9b86980dc
Timestamp: 1729768228 Timestamp [UCT]: 2024-10-24 11:10:28 Age [y:d:h:m:s]: 00:030:17:34:39
Block: 1138503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21951 RingCT/type: yes/0
Extra: 011cdf32fdcccc68b9f46d20050c7497ec0d45a11d17f85a86384087d9b86980dc0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c3ff392ad8d838b787fc1bae3ae97e42c7175db4077df4bb2919ea4524fc2f8 0.600000000000 1622184 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": 1138513, "vin": [ { "gen": { "height": 1138503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c3ff392ad8d838b787fc1bae3ae97e42c7175db4077df4bb2919ea4524fc2f8" } } ], "extra": [ 1, 28, 223, 50, 253, 204, 204, 104, 185, 244, 109, 32, 5, 12, 116, 151, 236, 13, 69, 161, 29, 23, 248, 90, 134, 56, 64, 135, 217, 184, 105, 128, 220, 2, 17, 0, 0, 0, 1, 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