Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 192ac7d4dce7d61872b5e3adf91422a077edca89453e74902520ca3bc2342038

Tx prefix hash: 0c591455d17f4e6b32ea769f16bb3b8cd7a743cbe3634705cf60ce77d0497938
Tx public key: 26370a9dc998e46d04c682e2760454e31f4a097f1e159ac01283beb50ed82e23
Timestamp: 1645305742 Timestamp [UCT]: 2022-02-19 21:22:22 Age [y:d:h:m:s]: 02:359:18:44:10
Block: 442170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776305 RingCT/type: yes/0
Extra: 0126370a9dc998e46d04c682e2760454e31f4a097f1e159ac01283beb50ed82e23021100000009c9067537000000000000000000

1 output(s) for total of 21.033305351000 dcy

stealth address amount amount idx
00: e9449b563139268cb18c0a2d8aeadd4e263e4e013b0d57bf4b26cf6a479f4055 21.033305351000 854893 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": 442180, "vin": [ { "gen": { "height": 442170 } } ], "vout": [ { "amount": 21033305351, "target": { "key": "e9449b563139268cb18c0a2d8aeadd4e263e4e013b0d57bf4b26cf6a479f4055" } } ], "extra": [ 1, 38, 55, 10, 157, 201, 152, 228, 109, 4, 198, 130, 226, 118, 4, 84, 227, 31, 74, 9, 127, 30, 21, 154, 192, 18, 131, 190, 181, 14, 216, 46, 35, 2, 17, 0, 0, 0, 9, 201, 6, 117, 55, 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