Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965f97e9da8950ae869b2ff7d2a21a30fa4e325279be122b949a7d8f909ae7cc

Tx prefix hash: a9b147ed32774e553a261a844ca647261b4d8e7c72fbd65e4dd456cbced03c23
Tx public key: bf353dd9443e321705191f933733dd9202d5ea9dacad395299b13315c0c832d7
Timestamp: 1656920204 Timestamp [UCT]: 2022-07-04 07:36:44 Age [y:d:h:m:s]: 02:185:16:22:19
Block: 536314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 654057 RingCT/type: yes/0
Extra: 01bf353dd9443e321705191f933733dd9202d5ea9dacad395299b13315c0c832d7021100000001a8c141c5000000000000000000

1 output(s) for total of 10.255792745000 dcy

stealth address amount amount idx
00: b07feba316e24d2068ecfe18a4a1a730d3a5cc9c113e6f57b2dca051bff8ee1b 10.255792745000 966055 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": 536324, "vin": [ { "gen": { "height": 536314 } } ], "vout": [ { "amount": 10255792745, "target": { "key": "b07feba316e24d2068ecfe18a4a1a730d3a5cc9c113e6f57b2dca051bff8ee1b" } } ], "extra": [ 1, 191, 53, 61, 217, 68, 62, 50, 23, 5, 25, 31, 147, 55, 51, 221, 146, 2, 213, 234, 157, 172, 173, 57, 82, 153, 177, 51, 21, 192, 200, 50, 215, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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