Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e449700ab252414caee60682bfdb7864962cfd589b193391a5f1a0a3bf5a629

Tx prefix hash: badaef5b7f0e23e6bc962cab62a6f0fe7788a11eb21245632e0152d037e77c3d
Tx public key: f18823e0acc4f7385d35ac2e5cd33ce34c8e96e2b0fd7bbc7926b5368501447b
Timestamp: 1711299470 Timestamp [UCT]: 2024-03-24 16:57:50 Age [y:d:h:m:s]: 01:023:16:17:27
Block: 985446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277880 RingCT/type: yes/0
Extra: 01f18823e0acc4f7385d35ac2e5cd33ce34c8e96e2b0fd7bbc7926b5368501447b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e43946d1e30762b04d848e0bf8fa5f64db1cfb1f74c1a2fc78020ce846ff9d 0.600000000000 1445657 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": 985456, "vin": [ { "gen": { "height": 985446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e43946d1e30762b04d848e0bf8fa5f64db1cfb1f74c1a2fc78020ce846ff9d" } } ], "extra": [ 1, 241, 136, 35, 224, 172, 196, 247, 56, 93, 53, 172, 46, 92, 211, 60, 227, 76, 142, 150, 226, 176, 253, 123, 188, 121, 38, 181, 54, 133, 1, 68, 123, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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