Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff19abdce4c4f305a3e0061aebafeebc981756fceca9aabcbf931d004f1d7667

Tx prefix hash: 2bd139f9fb3b8f364be774261c38047cc1b37e794b34ef7a855c35398a231c18
Tx public key: 22ef29d33935db307edff144565f5373d9b8d2a4044aae219b98d3929ab5c2e1
Timestamp: 1703161299 Timestamp [UCT]: 2023-12-21 12:21:39 Age [y:d:h:m:s]: 01:143:13:24:07
Block: 917949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363749 RingCT/type: yes/0
Extra: 0122ef29d33935db307edff144565f5373d9b8d2a4044aae219b98d3929ab5c2e10211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73b41b94049a01fc871fd4b4a2943ae5cf8d2fc292b8a337ea68523baf0d24e0 0.600000000000 1375577 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": 917959, "vin": [ { "gen": { "height": 917949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73b41b94049a01fc871fd4b4a2943ae5cf8d2fc292b8a337ea68523baf0d24e0" } } ], "extra": [ 1, 34, 239, 41, 211, 57, 53, 219, 48, 126, 223, 241, 68, 86, 95, 83, 115, 217, 184, 210, 164, 4, 74, 174, 33, 155, 152, 211, 146, 154, 181, 194, 225, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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