Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a800e4e10cd21e9782d513062902ae3fb8d6d22fcdf559e47f248a33686e0257

Tx prefix hash: e62a9c434d5943308b51da70995e1e428fa060cf1c9ac04cb745ec39dc4285a9
Tx public key: 16d248e58a3694d3481fdfeef813a4b5d2655e95e1823a510ba5081739e5a9a8
Timestamp: 1735160417 Timestamp [UCT]: 2024-12-25 21:00:17 Age [y:d:h:m:s]: 00:095:14:13:44
Block: 1183133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68094 RingCT/type: yes/0
Extra: 0116d248e58a3694d3481fdfeef813a4b5d2655e95e1823a510ba5081739e5a9a80211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6773a40d7391bc3c32a6a4c01311d55452c4e1094dadd1424ecc95c0ff575529 0.600000000000 1669574 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": 1183143, "vin": [ { "gen": { "height": 1183133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6773a40d7391bc3c32a6a4c01311d55452c4e1094dadd1424ecc95c0ff575529" } } ], "extra": [ 1, 22, 210, 72, 229, 138, 54, 148, 211, 72, 31, 223, 238, 248, 19, 164, 181, 210, 101, 94, 149, 225, 130, 58, 81, 11, 165, 8, 23, 57, 229, 169, 168, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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