Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57ad6e8dc14ae7e2b167a17f8775683e099dc4e87ac8c92bbc18fb4abe06a557

Tx prefix hash: 13a0e4aa16dce31d75d234d26848cde9567147deefea206e07bcbf29413de759
Tx public key: be0ad3e6e985ec22015f772fd98a65772b47d2172ad25cce49998c2c7da6544f
Timestamp: 1736862934 Timestamp [UCT]: 2025-01-14 13:55:34 Age [y:d:h:m:s]: 00:155:04:41:09
Block: 1197213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110614 RingCT/type: yes/0
Extra: 01be0ad3e6e985ec22015f772fd98a65772b47d2172ad25cce49998c2c7da6544f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0834e7e2b123a87f8c227a8d35ca0fe4da00a24d8224e6e6b0a82fb05e3b2b9 0.600000000000 1683820 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": 1197223, "vin": [ { "gen": { "height": 1197213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0834e7e2b123a87f8c227a8d35ca0fe4da00a24d8224e6e6b0a82fb05e3b2b9" } } ], "extra": [ 1, 190, 10, 211, 230, 233, 133, 236, 34, 1, 95, 119, 47, 217, 138, 101, 119, 43, 71, 210, 23, 42, 210, 92, 206, 73, 153, 140, 44, 125, 166, 84, 79, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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