← previous blocknext block →recent activity
Analyzing
Block #86,308,706
25 transactions · 17 stateful · 2026-07-08 01:25:30 UTC
Parallelism
88/100
Blocked
47%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,308,706 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w011w114w215w016w117w218w122w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb4c35fcd…43ae
0xa6afd3…d132
4 touches
1 conflict
0xe87be23b…71e4
0x40c49f…2af0
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xfadb0e19…7a27
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x89750670…2dea
0xa6afd3…d132
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity