← previous blocknext block →recent activity
Analyzing
Block #86,259,234
20 transactions · 18 stateful · 2026-07-07 19:55:21 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,259,234 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w312w013w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0efc210e…70ab
0x34b655…2a6f
8 touches
6 conflicts
0xb5f244d5…f550
0x34b655…2a6f
6 touches
3 conflicts
0x7d1a4e77…57d9
0x34b655…2a6f
6 touches
3 conflicts
0x30ae635d…5e67
0x34b655…2a6f
6 touches
3 conflicts
0x5138188e…796b
0x34b655…2a6f
6 touches
3 conflicts
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity