← previous blocknext block →recent activity
Analyzing
Block #86,383,808
16 transactions · 14 stateful · 2026-07-08 09:47:22 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,383,808 · 16 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
2w08w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ebe108b…72a0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0a2287c1…aba7
0x34b655…2a6f
2 touches
0 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x2c2761c0…476e
0x34b655…2a6f
2 touches
0 conflicts
0x5b2ddfcc…f6cd
0x34b655…2a6f
2 touches
0 conflicts
0x6cb58e92…fa8c
0x34b655…2a6f
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 0x1ebe108b2e…c472a0
Audit this contract →
← previous block·next block →recent activity