Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adbc3a0a05f264a041538537a9833c3f516d111e3be07424d6b81854d4ecb973

Tx prefix hash: 20fde4d133e1c1994439e413cfb6a99a484540c4580cc358aeae50d3b89da934
Tx public key: 75e014696c522363ed9f70197cad86a2bc43998da1ebdc4a7a3f100c14b49e11
Timestamp: 1699199800 Timestamp [UCT]: 2023-11-05 15:56:40 Age [y:d:h:m:s]: 01:199:21:52:27
Block: 885111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404109 RingCT/type: yes/0
Extra: 0175e014696c522363ed9f70197cad86a2bc43998da1ebdc4a7a3f100c14b49e110211000000014b8f5122000000000000000000

1 output(s) for total of 0.716572002000 dcy

stealth address amount amount idx
00: 8011b57b9841c4558477dc4f6d021b7f876a316dfbc293bf65804a236bae5f11 0.716572002000 1340864 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": 885121, "vin": [ { "gen": { "height": 885111 } } ], "vout": [ { "amount": 716572002, "target": { "key": "8011b57b9841c4558477dc4f6d021b7f876a316dfbc293bf65804a236bae5f11" } } ], "extra": [ 1, 117, 224, 20, 105, 108, 82, 35, 99, 237, 159, 112, 25, 124, 173, 134, 162, 188, 67, 153, 141, 161, 235, 220, 74, 122, 63, 16, 12, 20, 180, 158, 17, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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