Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af79200825faff81c96d4c7025044f86a20a779f31178c538ae829e628ce3b9d

Tx prefix hash: 504aba9af619bf7abfed7f16585858fe254fd0944c7d168efa67a3feada615f7
Tx public key: 46ee3b1e191e58698e71c7bf4bcd398f8ab90cb5e9669ecaa340fd2f0200c692
Timestamp: 1677892383 Timestamp [UCT]: 2023-03-04 01:13:03 Age [y:d:h:m:s]: 01:261:23:02:47
Block: 709353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448113 RingCT/type: yes/0
Extra: 0146ee3b1e191e58698e71c7bf4bcd398f8ab90cb5e9669ecaa340fd2f0200c6920211000000035029cbac000000000000000000

1 output(s) for total of 2.739169733000 dcy

stealth address amount amount idx
00: 3e4b83a6ef54dae6c4f5f67d9d615e1ebb58560f66568e1acd45d38028d6c1e3 2.739169733000 1153332 of 0

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": 709363, "vin": [ { "gen": { "height": 709353 } } ], "vout": [ { "amount": 2739169733, "target": { "key": "3e4b83a6ef54dae6c4f5f67d9d615e1ebb58560f66568e1acd45d38028d6c1e3" } } ], "extra": [ 1, 70, 238, 59, 30, 25, 30, 88, 105, 142, 113, 199, 191, 75, 205, 57, 143, 138, 185, 12, 181, 233, 102, 158, 202, 163, 64, 253, 47, 2, 0, 198, 146, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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