← previous blocknext block →recent activity
Analyzing
Block #86,054,811
28 transactions · 19 stateful · 2026-07-06 21:10:42 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,054,811 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w018w119w021w123w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x2108d7bc…f31b
0x065c9d…c394
2 touches
0 conflicts
0x4bb3188a…8e1b
0x065c9d…c394
2 touches
0 conflicts
0xb4ebe6d1…fce3
0x065c9d…c394
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 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity