← previous blocknext block →recent activity
Analyzing
Block #86,156,835
22 transactions · 19 stateful · 2026-07-07 08:31:31 UTC
Parallelism
91/100
Blocked
21%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,156,835 · 22 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
2w03w07w08w114w015w116w117w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4cb048e…7562
0x34b655…2a6f
4 touches
1 conflict
0x518f2037…e422
0xa6afd3…d132
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xde398ff4…00ca
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x05edf2cf…ac3c
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x1722b8e6…4f9d
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
1 conflict on slot 0xc4cb048ec1…6f7562
Audit this contract →
← previous block·next block →recent activity