Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17511bd2a06f576ed3509bfd61c49523ed050a585f10a694e60a1fe48db4a8f

Tx prefix hash: 352e44860766406f67f090377a9f560d549d4cbc4f0dc6bc9a2946e57060b601
Tx public key: 8d1399dc26886c21a210c28468c34accab2c308e96c4af5bce06ae7c0e18e164
Timestamp: 1672145691 Timestamp [UCT]: 2022-12-27 12:54:51 Age [y:d:h:m:s]: 02:153:00:14:01
Block: 661700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 631085 RingCT/type: yes/0
Extra: 018d1399dc26886c21a210c28468c34accab2c308e96c4af5bce06ae7c0e18e164021100000001e7ace25d000000000000000000

1 output(s) for total of 3.940153893000 dcy

stealth address amount amount idx
00: 711d90e4a424be1281e6712a4b51ca591f5d4188299038d64756932c17fcce39 3.940153893000 1102493 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": 661710, "vin": [ { "gen": { "height": 661700 } } ], "vout": [ { "amount": 3940153893, "target": { "key": "711d90e4a424be1281e6712a4b51ca591f5d4188299038d64756932c17fcce39" } } ], "extra": [ 1, 141, 19, 153, 220, 38, 136, 108, 33, 162, 16, 194, 132, 104, 195, 74, 204, 171, 44, 48, 142, 150, 196, 175, 91, 206, 6, 174, 124, 14, 24, 225, 100, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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