Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f401ff06c6c0eff8a5a570022b4e399ed0a5b865a22eb4dc9f4c95765b621a3e

Tx prefix hash: a6ba1a74f1e844685957465874829a947a5e84a59c489c0520a1ba673c707703
Tx public key: b407a488a5583ddd7bd05e4aa72d9a93998e0aa93f4dc43b915d7df81322b9e1
Timestamp: 1705363169 Timestamp [UCT]: 2024-01-15 23:59:29 Age [y:d:h:m:s]: 01:157:17:14:59
Block: 936190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373701 RingCT/type: yes/0
Extra: 01b407a488a5583ddd7bd05e4aa72d9a93998e0aa93f4dc43b915d7df81322b9e10211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8435262155c08137d1dc3efde74c16059e3b564299c1cebf9461659733dba09 0.600000000000 1394214 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": 936200, "vin": [ { "gen": { "height": 936190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8435262155c08137d1dc3efde74c16059e3b564299c1cebf9461659733dba09" } } ], "extra": [ 1, 180, 7, 164, 136, 165, 88, 61, 221, 123, 208, 94, 74, 167, 45, 154, 147, 153, 142, 10, 169, 63, 77, 196, 59, 145, 93, 125, 248, 19, 34, 185, 225, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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