← previous blocknext block →recent activity
Analyzing
Block #83,890,345
17 transactions · 14 stateful · 2026-06-26 20:43:28 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,890,345 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w28w010w114w015w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32229dd3…4dbb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xec85756f…0ba2
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x32229dd3a6…874dbb
Audit this contract →
← previous block·next block →recent activity