← previous blocknext block →recent activity
Analyzing
Block #86,834,374
24 transactions · 23 stateful · 2026-07-10 12:00:38 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,834,374 · 24 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
1w03w04w05w16w27w08w19w210w111w214w015w117w319w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff2c0517…acf7
0x34b655…2a6f
8 touches
6 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x68d518d8…3932
0x34b655…2a6f
4 touches
1 conflict
0x6d99ac64…0aa3
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 0xff2c051742…97acf7
Audit this contract →
← previous block·next block →recent activity