← previous blocknext block →recent activity
Analyzing
Block #86,628,819
23 transactions · 19 stateful · 2026-07-09 13:06:11 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,628,819 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w114w016w117w218w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x4ec8d1b4…4e6e
0x34b655…2a6f
6 touches
3 conflicts
0x5d537073…cf27
0x34b655…2a6f
6 touches
3 conflicts
0x70ff9262…8d80
0x34b655…2a6f
6 touches
3 conflicts
0x250c8181…eef2
0x34b655…2a6f
4 touches
1 conflict
0x5895d195…9f38
0x34b655…2a6f
4 touches
1 conflict
0x5b101190…060e
0x34b655…2a6f
4 touches
1 conflict
0x5b30a6e6…b249
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity