← previous blocknext block →recent activity
Analyzing
Block #86,443,947
23 transactions · 19 stateful · 2026-07-08 16:28:56 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,443,947 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w113w114w215w316w417w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0xb0bc3bf8…e2b1
0x34b655…2a6f
6 touches
3 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
6 touches
3 conflicts
0xedcf2991…8551
0x34b655…2a6f
4 touches
2 conflicts
0x819b5176…86cf
0x34b655…2a6f
4 touches
1 conflict
0x987cdcd5…d990
0x34b655…2a6f
4 touches
1 conflict
0xa4658f5c…b257
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity