Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cf9ca11d083f9ca4edfd0e7bf933ffd821cd90c37a3126baa636a50c3341c23

Tx prefix hash: 609b293f0b2921e70ff5ff221dcf7335236e96ee876b7b2ca5ec822ea5b31198
Tx public key: 069a01bea9bfdb125b26322e90060fa93dd5fda04001a7e6eeaa2feb374d954b
Timestamp: 1736315538 Timestamp [UCT]: 2025-01-08 05:52:18 Age [y:d:h:m:s]: 00:303:08:59:30
Block: 1192676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214327 RingCT/type: yes/0
Extra: 01069a01bea9bfdb125b26322e90060fa93dd5fda04001a7e6eeaa2feb374d954b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 012aa53094dd97482f472fa32f1378c7ac4385033641099edeca9a823b78a75a 0.600000000000 1679231 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": 1192686, "vin": [ { "gen": { "height": 1192676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "012aa53094dd97482f472fa32f1378c7ac4385033641099edeca9a823b78a75a" } } ], "extra": [ 1, 6, 154, 1, 190, 169, 191, 219, 18, 91, 38, 50, 46, 144, 6, 15, 169, 61, 213, 253, 160, 64, 1, 167, 230, 238, 170, 47, 235, 55, 77, 149, 75, 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