← previous blocknext block →recent activity
Analyzing
Block #86,232,474
24 transactions · 19 stateful · 2026-07-07 16:56:31 UTC
Parallelism
83/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,232,474 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w07w18w210w113w214w015w016w117w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2877f440…c2c8
0x34b655…2a6f
8 touches
6 conflicts
0xac206e47…ef7d
0x34b655…2a6f
6 touches
3 conflicts
0x4bc0441e…58bb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0008
0x86dbf0…eb2d
6 touches
3 conflicts
0x301e1c77…9e30
0x34b655…2a6f
6 touches
3 conflicts
0x61d65579…ee3c
0xad96c3…8d7c
6 touches
3 conflicts
0xd821cffd…3ff0
0x754704…b603
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
6 conflicts on slot 0x2877f4400c…13c2c8
Audit this contract →
← previous block·next block →recent activity