Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c29d0e797c98317d18edb44404169829edbd61c06922fa71223efce55aedaed

Tx prefix hash: eb0a1b18b0ae8ca98f1a8d844647a1e72ccf79801a34c9ec2190d1ea10b6aa94
Tx public key: e77bc743431c65167c08d64f7bf8e9b55a71a06ab4c065ace3ca05f94ce44ee2
Timestamp: 1726138804 Timestamp [UCT]: 2024-09-12 11:00:04 Age [y:d:h:m:s]: 00:101:08:33:25
Block: 1108443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72518 RingCT/type: yes/0
Extra: 01e77bc743431c65167c08d64f7bf8e9b55a71a06ab4c065ace3ca05f94ce44ee2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: ae670f45aea9016afc981ba7348f30eb834934f9bb35fc4e3f7bbc5b12d7c3af 0.600200000000 1586340 of 0

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": 1108453, "vin": [ { "gen": { "height": 1108443 } } ], "vout": [ { "amount": 600200000, "target": { "key": "ae670f45aea9016afc981ba7348f30eb834934f9bb35fc4e3f7bbc5b12d7c3af" } } ], "extra": [ 1, 231, 123, 199, 67, 67, 28, 101, 22, 124, 8, 214, 79, 123, 248, 233, 181, 90, 113, 160, 106, 180, 192, 101, 172, 227, 202, 5, 249, 76, 228, 78, 226, 2, 17, 0, 0, 0, 3, 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