Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a42fe21f8d7e4086960ea619ad5f15da597a0befcffab902ff71b56410b6eae

Tx prefix hash: eca788aceda90a1c9eadb0697cc24bc8f80dbdf91d3773a7794a8ee384ca2589
Tx public key: fbf5a1d75788eb2789a7e1683a4a7e7ff3a61b003486a4baf687f762f1e8d5ab
Timestamp: 1685795054 Timestamp [UCT]: 2023-06-03 12:24:14 Age [y:d:h:m:s]: 02:161:16:58:45
Block: 774225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 635348 RingCT/type: yes/0
Extra: 01fbf5a1d75788eb2789a7e1683a4a7e7ff3a61b003486a4baf687f762f1e8d5ab021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.669826491000 dcy

stealth address amount amount idx
00: fd74de9ff53c2e5f9ee930f155500aedf7e5464e5d6dfd3e2aed9b579c70dbe0 1.669826491000 1223694 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": 774235, "vin": [ { "gen": { "height": 774225 } } ], "vout": [ { "amount": 1669826491, "target": { "key": "fd74de9ff53c2e5f9ee930f155500aedf7e5464e5d6dfd3e2aed9b579c70dbe0" } } ], "extra": [ 1, 251, 245, 161, 215, 87, 136, 235, 39, 137, 167, 225, 104, 58, 74, 126, 127, 243, 166, 27, 0, 52, 134, 164, 186, 246, 135, 247, 98, 241, 232, 213, 171, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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