← previous blocknext block →recent activity
Analyzing
Block #86,362,738
13 transactions · 9 stateful · 2026-07-08 07:26:18 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,362,738 · 13 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x21a3ddc9…fe40
0x34b655…2a6f
3 touches
1 conflict
0x080c1dbe…ba16
0x2ab50b…5c41
2 touches
0 conflicts
0x0a5e8545…2c05
0x2ab50b…5c41
2 touches
0 conflicts
0x1449b49f…d1d8
0x2ab50b…5c41
2 touches
0 conflicts
0x15a8b5e6…0296
0x2ab50b…5c41
2 touches
0 conflicts
0x19e8d190…65f1
0x2ab50b…5c41
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 0x5e2ea201dc…2012de
Audit this contract →
← previous block·next block →recent activity