Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff50b9fb42287977601f1f3124d54a0602a6aa37e771ff8b873b036d73a1c35e

Tx prefix hash: e1ae46e221ef24bea40178abc0551dce61c60e90d29be8d5d95ad2aad31679c7
Tx public key: fe3e545adb25ef8192733442cde0ead923812fb6674d724e2f4682370f543c81
Timestamp: 1726342117 Timestamp [UCT]: 2024-09-14 19:28:37 Age [y:d:h:m:s]: 01:054:14:20:02
Block: 1110136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297436 RingCT/type: yes/0
Extra: 01fe3e545adb25ef8192733442cde0ead923812fb6674d724e2f4682370f543c8102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd5e3e880123153125a0f5d5220445ef8997a40fdf7aae52719b343a795bd3f1 0.600000000000 1588633 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": 1110146, "vin": [ { "gen": { "height": 1110136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd5e3e880123153125a0f5d5220445ef8997a40fdf7aae52719b343a795bd3f1" } } ], "extra": [ 1, 254, 62, 84, 90, 219, 37, 239, 129, 146, 115, 52, 66, 205, 224, 234, 217, 35, 129, 47, 182, 103, 77, 114, 78, 47, 70, 130, 55, 15, 84, 60, 129, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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