← previous blocknext block →recent activity
Analyzing
Block #83,400,125
18 transactions · 15 stateful · 2026-06-24 14:12:06 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,400,125 · 18 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
1w02w03w16w07w19w212w315w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758bd24b…cc0c
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x0835adb5…ad83
0x34b655…2a6f
4 touches
1 conflict
0x13aceb70…cf9f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2503ac3b…df13
0x34b655…2a6f
4 touches
1 conflict
0x4f2daaf7…f9e7
0x34b655…2a6f
4 touches
1 conflict
0x86c1c7e7…53c2
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
6 conflicts on slot 0x758bd24bd8…71cc0c
Audit this contract →
← previous block·next block →recent activity