Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f0c3533adf06101e5fe76a8e9539828111e48762b481fc26a6190a5d8b905e3

Tx prefix hash: 3166dc28906f41bb93b43ef6f8e129da8163f0339c33ac59d197d2ec3b00192c
Tx public key: 53ebf79ed697f346af458aa8c8c2d951481c6d4fd1dfcb10573c40ef0baf1220
Timestamp: 1736521627 Timestamp [UCT]: 2025-01-10 15:07:07 Age [y:d:h:m:s]: 00:158:23:03:53
Block: 1194383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113313 RingCT/type: yes/0
Extra: 0153ebf79ed697f346af458aa8c8c2d951481c6d4fd1dfcb10573c40ef0baf1220021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d32ba9c8facf5277e62a404e0ea72257d09ed2a79854005382db49c47693b982 0.600000000000 1680954 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": 1194393, "vin": [ { "gen": { "height": 1194383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d32ba9c8facf5277e62a404e0ea72257d09ed2a79854005382db49c47693b982" } } ], "extra": [ 1, 83, 235, 247, 158, 214, 151, 243, 70, 175, 69, 138, 168, 200, 194, 217, 81, 72, 28, 109, 79, 209, 223, 203, 16, 87, 60, 64, 239, 11, 175, 18, 32, 2, 17, 0, 0, 0, 1, 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