Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2bba214381a116e841b359c221374864c2e403d8f685a30730a6446019ad1ca

Tx prefix hash: 3653556fc9d291078b99408172fe1290a76da507ec15777aafd6c6ebe1f9dc00
Tx public key: d261bd08b86cd1e6dc07bf2eb20cffb11d7e1e0f11a3e8683c7b84ba6e47dc04
Timestamp: 1725727464 Timestamp [UCT]: 2024-09-07 16:44:24 Age [y:d:h:m:s]: 00:212:17:40:15
Block: 1105051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151864 RingCT/type: yes/0
Extra: 01d261bd08b86cd1e6dc07bf2eb20cffb11d7e1e0f11a3e8683c7b84ba6e47dc04021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06672a35d593a18c944e1adf870a3a837eb10d785fe5346a87341885b4fd34bb 0.600000000000 1582388 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": 1105061, "vin": [ { "gen": { "height": 1105051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06672a35d593a18c944e1adf870a3a837eb10d785fe5346a87341885b4fd34bb" } } ], "extra": [ 1, 210, 97, 189, 8, 184, 108, 209, 230, 220, 7, 191, 46, 178, 12, 255, 177, 29, 126, 30, 15, 17, 163, 232, 104, 60, 123, 132, 186, 110, 71, 220, 4, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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