← previous blocknext block →recent activity
Analyzing
Block #87,736,095
20 transactions · 18 stateful · 2026-07-14 16:30:45 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,736,095 · 20 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
1w02w14w05w26w07w112w014w115w216w319w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb3774c5…2442
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x094b78c4…9170
0x34b655…2a6f
4 touches
1 conflict
0x37ee30c9…9e70
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49a97bff…33ed
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 0xdb3774c5a5…c72442
Audit this contract →
← previous block·next block →recent activity