Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 573a0528e8f2a002013c4c709eeae08d52e9c32ea10f05acdbd1db5e5cba3d8f

Tx prefix hash: 5f5f5f77dc9be759314753b526340a6619477e1fe7c996f52ae5a15f71a35c08
Tx public key: fad6b8659af425bd9a18e624d15c8c8a99691800c886527ea7eda591d50bb9e9
Timestamp: 1735870397 Timestamp [UCT]: 2025-01-03 02:13:17 Age [y:d:h:m:s]: 00:301:15:54:39
Block: 1188996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213099 RingCT/type: yes/0
Extra: 01fad6b8659af425bd9a18e624d15c8c8a99691800c886527ea7eda591d50bb9e9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e014ba075b9a4dc1e70ef192e26a92699e175cfc6c851eea893dc19dcd5e10f 0.600000000000 1675501 of 15

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": 1189006, "vin": [ { "gen": { "height": 1188996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e014ba075b9a4dc1e70ef192e26a92699e175cfc6c851eea893dc19dcd5e10f" } } ], "extra": [ 1, 250, 214, 184, 101, 154, 244, 37, 189, 154, 24, 230, 36, 209, 92, 140, 138, 153, 105, 24, 0, 200, 134, 82, 126, 167, 237, 165, 145, 213, 11, 185, 233, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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