← previous blocknext block →recent activity
Analyzing
Block #86,966,447
16 transactions · 15 stateful · 2026-07-11 02:43:26 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,966,447 · 16 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
1w02w14w05w16w28w09w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d84bebc…07d1
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
3 conflicts
0x1d84bebc…07d0
0x34b655…2a6f
6 touches
3 conflicts
0xe873c138…e577
0x34b655…2a6f
5 touches
3 conflicts
0x48a29a03…c43b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
3 conflicts on slot 0x1d84bebc66…b107d1
Audit this contract →
← previous block·next block →recent activity