Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9ce82065cfb0cb25635bb623f852e9f66447b191167d5ca1e530656815d6747

Tx prefix hash: 4faa854151db608f933b1dea9c7fb2657ab65f926a65fb2bd571e13d6534be3a
Tx public key: c0da8908ceb2b8568bedb0c29245491f1403467b50f635e83d1b243b2a624a4a
Timestamp: 1702187900 Timestamp [UCT]: 2023-12-10 05:58:20 Age [y:d:h:m:s]: 01:115:19:34:14
Block: 909890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343903 RingCT/type: yes/0
Extra: 01c0da8908ceb2b8568bedb0c29245491f1403467b50f635e83d1b243b2a624a4a02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c60be9a47b9b20d114fc31a1ff493e85931e5a31014d02548ba01a61f2fac22 0.600000000000 1367019 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": 909900, "vin": [ { "gen": { "height": 909890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c60be9a47b9b20d114fc31a1ff493e85931e5a31014d02548ba01a61f2fac22" } } ], "extra": [ 1, 192, 218, 137, 8, 206, 178, 184, 86, 139, 237, 176, 194, 146, 69, 73, 31, 20, 3, 70, 123, 80, 246, 53, 232, 61, 27, 36, 59, 42, 98, 74, 74, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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