Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af559cb112a61fdc1c08f65fd5ffe9f3aa79c43679c2a7f22717a0295c8a5eff

Tx prefix hash: d10f59fcbdd2e13d03cf5321c97192555d5783a322f4f9d33d0e6bb61d78be18
Tx public key: aaf30e06118d1d617c084638a5026e1d83d65ce115dedd504676b64eae2439a6
Timestamp: 1663498243 Timestamp [UCT]: 2022-09-18 10:50:43 Age [y:d:h:m:s]: 02:119:23:42:04
Block: 590549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607268 RingCT/type: yes/0
Extra: 01aaf30e06118d1d617c084638a5026e1d83d65ce115dedd504676b64eae2439a6021100000001e6d27f9c000000000000000000

1 output(s) for total of 6.780868193000 dcy

stealth address amount amount idx
00: 4c7e3e3fddc95d0c1cc96aac8b950b5971403d8891a37b7e0fdc2dfbd065b2f9 6.780868193000 1024974 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": 590559, "vin": [ { "gen": { "height": 590549 } } ], "vout": [ { "amount": 6780868193, "target": { "key": "4c7e3e3fddc95d0c1cc96aac8b950b5971403d8891a37b7e0fdc2dfbd065b2f9" } } ], "extra": [ 1, 170, 243, 14, 6, 17, 141, 29, 97, 124, 8, 70, 56, 165, 2, 110, 29, 131, 214, 92, 225, 21, 222, 221, 80, 70, 118, 182, 78, 174, 36, 57, 166, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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