Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5c5e0c44e9eb0a1ade51cbec770af4e5ada1ade1e1f125a1bf07cb26552cfb4

Tx prefix hash: 29696317e3916a640a6fe939342345472a36c23948b11cb6d33c4c044f79cc5a
Tx public key: 9e32be8ab1fe5aa86ff29412348c3b283eab6a2affd74154ec5d54d5f70431f4
Timestamp: 1684372106 Timestamp [UCT]: 2023-05-18 01:08:26 Age [y:d:h:m:s]: 01:240:08:34:59
Block: 762433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433224 RingCT/type: yes/0
Extra: 019e32be8ab1fe5aa86ff29412348c3b283eab6a2affd74154ec5d54d5f70431f402110000000175e3f0e9000000000000000000

1 output(s) for total of 1.827019383000 dcy

stealth address amount amount idx
00: 5d98e9f43adbcf549d7b001a2b480255261cf16cac37eb02dd933ed8b28689a7 1.827019383000 1211182 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": 762443, "vin": [ { "gen": { "height": 762433 } } ], "vout": [ { "amount": 1827019383, "target": { "key": "5d98e9f43adbcf549d7b001a2b480255261cf16cac37eb02dd933ed8b28689a7" } } ], "extra": [ 1, 158, 50, 190, 138, 177, 254, 90, 168, 111, 242, 148, 18, 52, 140, 59, 40, 62, 171, 106, 42, 255, 215, 65, 84, 236, 93, 84, 213, 247, 4, 49, 244, 2, 17, 0, 0, 0, 1, 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