Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7be37815b385e6334274c6a399563cb3606c8efdbed17afaeaf1a841e6fe6a55

Tx prefix hash: 72abaaac22058cfce7832f64ec22c4383b5207eac4d1a7ba584dfcc98493dfba
Tx public key: 34a9fdfd40f4bd26823b5f195e9c59e1e3695d920e9832f89da72a142eaba110
Timestamp: 1723573365 Timestamp [UCT]: 2024-08-13 18:22:45 Age [y:d:h:m:s]: 00:165:15:18:32
Block: 1087182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118446 RingCT/type: yes/0
Extra: 0134a9fdfd40f4bd26823b5f195e9c59e1e3695d920e9832f89da72a142eaba110021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba4d7b6b7d71758e28f8ebb056e6860d5ccac7eaa01fe6160e6bfbc988bcd6de 0.600000000000 1561787 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": 1087192, "vin": [ { "gen": { "height": 1087182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba4d7b6b7d71758e28f8ebb056e6860d5ccac7eaa01fe6160e6bfbc988bcd6de" } } ], "extra": [ 1, 52, 169, 253, 253, 64, 244, 189, 38, 130, 59, 95, 25, 94, 156, 89, 225, 227, 105, 93, 146, 14, 152, 50, 248, 157, 167, 42, 20, 46, 171, 161, 16, 2, 17, 0, 0, 0, 19, 233, 20, 221, 21, 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