← previous blocknext block →recent activity
Analyzing
Block #86,980,864
16 transactions · 13 stateful · 2026-07-11 04:19:44 UTC
Parallelism
56/100
Blocked
54%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,980,864 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w39w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x814f0f40…c654
0x34b655…2a6f
6 touches
3 conflicts
0x6dcb5d8d…5f07
0x34b655…2a6f
4 touches
1 conflict
0x89cf3cb2…b612
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity