← previous blocknext block →recent activity
Analyzing
Block #86,848,823
14 transactions · 10 stateful · 2026-07-10 13:37:09 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,848,823 · 14 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
3w04w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e5933c1…2063
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xec7fe04a…3c56
0x34b655…2a6f
4 touches
1 conflict
0x2ead5a0b…3978
0x34b655…2a6f
2 touches
0 conflicts
0x3cc5e445…621e
0x34b655…2a6f
2 touches
0 conflicts
0x44d24653…fa2f
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5318
0x34b655…2a6f
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 0x0e5933c18d…cd2063
Audit this contract →
← previous block·next block →recent activity