← previous blocknext block →recent activity
Analyzing
Block #83,936,202
12 transactions · 11 stateful · 2026-06-27 01:49:02 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,936,202 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19bfb0e5…73b4
0x34b655…2a6f
4 touches
1 conflict
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x53b50546…79cf
0x34b655…2a6f
3 touches
1 conflict
0xf2a80255…d296
0x34b655…2a6f
3 touches
1 conflict
0x0d4c3350…d004
0x065c9d…c394
2 touches
0 conflicts
0xff96dc9b…93d7
0x065c9d…c394
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 0x19bfb0e559…d673b4
Audit this contract →
← previous block·next block →recent activity