Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7acf0411a4a10d10e36808e4c059015cd0a81802b1b543d6c2230547e58d722

Tx prefix hash: e825279360896d9cbe57ee7179cd1c9628971a0bdb0a6b260a7b6776ae8207b1
Tx public key: 12ac8751ae08cd908cf56799ab1c4bf81a4659620ea8a4a5362e9a17f0979290
Timestamp: 1718779240 Timestamp [UCT]: 2024-06-19 06:40:40 Age [y:d:h:m:s]: 00:275:21:13:16
Block: 1047438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197137 RingCT/type: yes/0
Extra: 0112ac8751ae08cd908cf56799ab1c4bf81a4659620ea8a4a5362e9a17f09792900211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 888805028c01cd179cb0063c3cfd1ec095595e2b0e41c6e70f7e525d833b49d9 0.600000000000 1517265 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": 1047448, "vin": [ { "gen": { "height": 1047438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "888805028c01cd179cb0063c3cfd1ec095595e2b0e41c6e70f7e525d833b49d9" } } ], "extra": [ 1, 18, 172, 135, 81, 174, 8, 205, 144, 140, 245, 103, 153, 171, 28, 75, 248, 26, 70, 89, 98, 14, 168, 164, 165, 54, 46, 154, 23, 240, 151, 146, 144, 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