← previous blocknext block →recent activity
Analyzing
Block #83,940,828
16 transactions · 13 stateful · 2026-06-27 02:19:50 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,940,828 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xecd15055…82c3
0x065c9d…c394
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x9e21be1c…8191
0x065c9d…c394
3 touches
1 conflict
0x5fc9803e…ef0c
0x065c9d…c394
2 touches
0 conflicts
0x99d20c73…606c
0x065c9d…c394
2 touches
0 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x90a9e3f873…9117ab
Audit this contract →
← previous block·next block →recent activity