← previous blocknext block →recent activity
Analyzing
Block #86,192,789
22 transactions · 16 stateful · 2026-07-07 12:31:28 UTC
Parallelism
91/100
Blocked
31%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,192,789 · 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
1w02w15w06w110w014w116w119w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1f6bdbc…8dd2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0x17fc1fe5…5e01
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
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 0xf1f6bdbcbf…0c8dd2
Audit this contract →
← previous block·next block →recent activity