← previous blocknext block →recent activity
Analyzing
Block #86,830,430
19 transactions · 13 stateful · 2026-07-10 11:34:14 UTC
Parallelism
74/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,830,430 · 19 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
2w04w17w18w211w312w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7ab945c…597e
0x34b655…2a6f
8 touches
6 conflicts
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xfebaf6fc…61b5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc2db6e7a…d074
0x34b655…2a6f
4 touches
1 conflict
0xc3ac1732…1dbb
0x34b655…2a6f
4 touches
1 conflict
0xdfc58aa8…e1df
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 0xf7ab945c23…8a597e
Audit this contract →
← previous block·next block →recent activity