Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119f8b83fe63873789800129a55daf7d13816b82a58c07aa1a3d3804b7494b55

Tx prefix hash: 785c3481077a4ed4eebff11ba8622ed6d1cc581520f0b5fb4eae1862a51cf800
Tx public key: c6d297b4fc286b63d01a940708863e65b1094adb2f4bbac7a7801a0c2220a3b4
Timestamp: 1709275800 Timestamp [UCT]: 2024-03-01 06:50:00 Age [y:d:h:m:s]: 00:341:13:38:05
Block: 968660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244207 RingCT/type: yes/0
Extra: 01c6d297b4fc286b63d01a940708863e65b1094adb2f4bbac7a7801a0c2220a3b402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2fb60597602084c25ec930a966cab0b53eab8fc96e42d69ff561abf502c3d76 0.600000000000 1428477 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": 968670, "vin": [ { "gen": { "height": 968660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2fb60597602084c25ec930a966cab0b53eab8fc96e42d69ff561abf502c3d76" } } ], "extra": [ 1, 198, 210, 151, 180, 252, 40, 107, 99, 208, 26, 148, 7, 8, 134, 62, 101, 177, 9, 74, 219, 47, 75, 186, 199, 167, 128, 26, 12, 34, 32, 163, 180, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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