Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 123c8e405f7d22315121ec134845f6fa71b365ad357f0bb440f91307157cde36

Tx prefix hash: d0a2bbbee8dab34753cc3401e1af64dae9724f3af19eed221e5f95c1d5c53a87
Tx public key: c7f43b871e6ed01d0a6187104d5f7e99eaa2e422cb1cde1d7157894c3bd78a64
Timestamp: 1730092622 Timestamp [UCT]: 2024-10-28 05:17:02 Age [y:d:h:m:s]: 00:179:19:29:41
Block: 1141164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128330 RingCT/type: yes/0
Extra: 01c7f43b871e6ed01d0a6187104d5f7e99eaa2e422cb1cde1d7157894c3bd78a6402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa36b69107fb2e086ee387442a3835d1f4606360c99f7957d49af83bac1825b1 0.600000000000 1624971 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": 1141174, "vin": [ { "gen": { "height": 1141164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa36b69107fb2e086ee387442a3835d1f4606360c99f7957d49af83bac1825b1" } } ], "extra": [ 1, 199, 244, 59, 135, 30, 110, 208, 29, 10, 97, 135, 16, 77, 95, 126, 153, 234, 162, 228, 34, 203, 28, 222, 29, 113, 87, 137, 76, 59, 215, 138, 100, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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