Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1d7b2316e6859b33fae8aa04098bd5f6d33f9f1e5a269f95a4d2a63731bd0f1

Tx prefix hash: 37f205c0eebe66d4df159be3d9d2006a4e6f5099fcdb6f7aecd35a7422e30a4d
Tx public key: 412706987f709eff57f740e436d944affaf23cbacf28e25f365faeedd91c0ffb
Timestamp: 1704231210 Timestamp [UCT]: 2024-01-02 21:33:30 Age [y:d:h:m:s]: 01:104:01:43:18
Block: 926814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335499 RingCT/type: yes/0
Extra: 01412706987f709eff57f740e436d944affaf23cbacf28e25f365faeedd91c0ffb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26a34a3a0d408f2c6ce8ed03d6b3b172efc925a18ac9bd323bcd917da99e0c10 0.600000000000 1384612 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": 926824, "vin": [ { "gen": { "height": 926814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26a34a3a0d408f2c6ce8ed03d6b3b172efc925a18ac9bd323bcd917da99e0c10" } } ], "extra": [ 1, 65, 39, 6, 152, 127, 112, 158, 255, 87, 247, 64, 228, 54, 217, 68, 175, 250, 242, 60, 186, 207, 40, 226, 95, 54, 95, 174, 237, 217, 28, 15, 251, 2, 17, 0, 0, 0, 2, 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