Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed162f5a1948cf424f2f8d3be876b5255906dbc8029e1a11e3262433dc5923f1

Tx prefix hash: e4abb251c2cbabed90834bb8d040a7082f9227e72a894bcd22747c0abbd17c0f
Tx public key: 16171edd303b75df1a3b148c56fb3a90c0e5da749af8799e4bc69f998f95789d
Timestamp: 1716596136 Timestamp [UCT]: 2024-05-25 00:15:36 Age [y:d:h:m:s]: 00:244:20:32:38
Block: 1029345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175175 RingCT/type: yes/0
Extra: 0116171edd303b75df1a3b148c56fb3a90c0e5da749af8799e4bc69f998f95789d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f9e3c798fa6f29987d30a34f9bbb4e3f6922faa18a526b94dc581de6fad761d 0.600000000000 1497412 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": 1029355, "vin": [ { "gen": { "height": 1029345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f9e3c798fa6f29987d30a34f9bbb4e3f6922faa18a526b94dc581de6fad761d" } } ], "extra": [ 1, 22, 23, 30, 221, 48, 59, 117, 223, 26, 59, 20, 140, 86, 251, 58, 144, 192, 229, 218, 116, 154, 248, 121, 158, 75, 198, 159, 153, 143, 149, 120, 157, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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