Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8ce23c2f74498e0cfa524284dad7ac2f614d39177636043edf034a8dcbd729f

Tx prefix hash: 7eb7bb93ef9f18b733fe559e9d56f7696ccc9bcc49255c0e9d3b5b8434f2d534
Tx public key: 944ae360bde242649c09dac22f139d68c69feefe46ad6d0d9e46be67f928808c
Timestamp: 1725731028 Timestamp [UCT]: 2024-09-07 17:43:48 Age [y:d:h:m:s]: 01:061:06:39:38
Block: 1105071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302217 RingCT/type: yes/0
Extra: 01944ae360bde242649c09dac22f139d68c69feefe46ad6d0d9e46be67f928808c02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b32218ee52a12b4af5e9c5237d33fd70a433c8c9545564c1538d1420ce9abdd3 0.600000000000 1582408 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": 1105081, "vin": [ { "gen": { "height": 1105071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b32218ee52a12b4af5e9c5237d33fd70a433c8c9545564c1538d1420ce9abdd3" } } ], "extra": [ 1, 148, 74, 227, 96, 189, 226, 66, 100, 156, 9, 218, 194, 47, 19, 157, 104, 198, 159, 238, 254, 70, 173, 109, 13, 158, 70, 190, 103, 249, 40, 128, 140, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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