← previous blocknext block →recent activity
Analyzing
Block #86,456,102
22 transactions · 16 stateful · 2026-07-08 17:50:13 UTC
Parallelism
91/100
Blocked
13%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,456,102 · 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
1w05w110w014w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0xbf1561d7…4cc9
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
2 touches
0 conflicts
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 0xc0eb79d1cb…5529a4
Audit this contract →
← previous block·next block →recent activity