← previous blocknext block →recent activity
Analyzing
Block #86,851,446
27 transactions · 12 stateful · 2026-07-10 13:54:40 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,851,446 · 27 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
2w05w06w17w29w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x505d32fe…14ad
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3413a430…234a
0x34b655…2a6f
4 touches
1 conflict
0x3ed62d2c…5852
0x34b655…2a6f
4 touches
1 conflict
0x510c8ab3…95d5
0x34b655…2a6f
4 touches
1 conflict
0x588da1c1…6ae5
0x34b655…2a6f
4 touches
1 conflict
0x5f7f7286…d268
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 0x505d32fe09…f014ad
Audit this contract →
← previous block·next block →recent activity