← previous blocknext block →recent activity
Analyzing
Block #86,628,356
15 transactions · 12 stateful · 2026-07-09 13:03:06 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,628,356 · 15 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
6w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x29211c1a…4115
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x7ce93f3d…b70e
0x34b655…2a6f
4 touches
1 conflict
0x90bd9024…0911
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc9ba1c61…1c8e
0x34b655…2a6f
4 touches
1 conflict
0x2c8bf7d9…3cc7
0xc8689a…ee79
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
1 conflict on slot 0x00f245ce7e…641e10
Audit this contract →
← previous block·next block →recent activity