Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f018ed6de6706f3bb1ccf002f38710f83844ad6a35721fe770ff7b9577b19a66

Tx prefix hash: 3ed3b27325f6cee87415da2cf769c1aece6f8faeb421450eac0c94fe7d51b1f0
Tx public key: a335dd23a2f4f53039c577103cc7618156668983db6ea0dd0feba1d7eb26a862
Timestamp: 1706884781 Timestamp [UCT]: 2024-02-02 14:39:41 Age [y:d:h:m:s]: 01:304:12:20:57
Block: 948820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476450 RingCT/type: yes/0
Extra: 01a335dd23a2f4f53039c577103cc7618156668983db6ea0dd0feba1d7eb26a86202110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fef6e3f8022a19c0ebd61bbf2b36c9c3b641a171613a2f993e6db2b36e28246 0.600000000000 1407312 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": 948830, "vin": [ { "gen": { "height": 948820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fef6e3f8022a19c0ebd61bbf2b36c9c3b641a171613a2f993e6db2b36e28246" } } ], "extra": [ 1, 163, 53, 221, 35, 162, 244, 245, 48, 57, 197, 119, 16, 60, 199, 97, 129, 86, 102, 137, 131, 219, 110, 160, 221, 15, 235, 161, 215, 235, 38, 168, 98, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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