Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2150251d206877401957c1192b52956832b12231eedb93b418d76551c50149f

Tx prefix hash: fb29a5df5ce3022e3bd44e0de28563797776c24f9ac7b76353199e1511a3a8bc
Tx public key: d847059e6802b6dc1afe1b08eb34f7a2bcd984c259879f3ec2c9d39396170a0a
Timestamp: 1704823204 Timestamp [UCT]: 2024-01-09 18:00:04 Age [y:d:h:m:s]: 01:092:09:48:37
Block: 931707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327167 RingCT/type: yes/0
Extra: 01d847059e6802b6dc1afe1b08eb34f7a2bcd984c259879f3ec2c9d39396170a0a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 409111259ca27e86c860d6e6e0e89bbdf6e2e3c91ee6bfd2b13b2897bf47aed8 0.600000000000 1389611 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": 931717, "vin": [ { "gen": { "height": 931707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409111259ca27e86c860d6e6e0e89bbdf6e2e3c91ee6bfd2b13b2897bf47aed8" } } ], "extra": [ 1, 216, 71, 5, 158, 104, 2, 182, 220, 26, 254, 27, 8, 235, 52, 247, 162, 188, 217, 132, 194, 89, 135, 159, 62, 194, 201, 211, 147, 150, 23, 10, 10, 2, 17, 0, 0, 0, 5, 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