Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94c016ae22912bf7d050d147147951a92b24ffb2fbaab8e91a6eae69273c8ae2

Tx prefix hash: 2c558e5e15be7e04bdf2d73b2036edd136dbc007eb5486c4ace72d6e7caea9be
Tx public key: b3a837b322c9f6073c3552a9cc66e7d8f346f45bf2714a5bf325b2bbbbe515d2
Timestamp: 1672246931 Timestamp [UCT]: 2022-12-28 17:02:11 Age [y:d:h:m:s]: 02:138:21:16:23
Block: 662507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 621004 RingCT/type: yes/0
Extra: 01b3a837b322c9f6073c3552a9cc66e7d8f346f45bf2714a5bf325b2bbbbe515d2021100000002e7ace25d000000000000000000

1 output(s) for total of 3.915969111000 dcy

stealth address amount amount idx
00: d39699a8687f09597b88fd51df6a8de7f1a64da7b146751f41bf70855b2e8c8a 3.915969111000 1103360 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": 662517, "vin": [ { "gen": { "height": 662507 } } ], "vout": [ { "amount": 3915969111, "target": { "key": "d39699a8687f09597b88fd51df6a8de7f1a64da7b146751f41bf70855b2e8c8a" } } ], "extra": [ 1, 179, 168, 55, 179, 34, 201, 246, 7, 60, 53, 82, 169, 204, 102, 231, 216, 243, 70, 244, 91, 242, 113, 74, 91, 243, 37, 178, 187, 187, 229, 21, 210, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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