← previous blocknext block →recent activity
Analyzing
Block #86,848,438
15 transactions · 9 stateful · 2026-07-10 13:34:34 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,848,438 · 15 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
4w05w16w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7fe04a…3c56
0x34b655…2a6f
4 touches
1 conflict
0xe9d235e0…3a44
0x34b655…2a6f
4 touches
1 conflict
0xea9e7e38…819b
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x2fcaf77d…8bec
0x34b655…2a6f
4 touches
1 conflict
0x3c190da8…2a1b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56091b00…b694
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
1 conflict on slot 0xec7fe04ad1…2d3c56
Audit this contract →
← previous block·next block →recent activity