← previous blocknext block →recent activity
Analyzing
Block #87,594,411
13 transactions · 11 stateful · 2026-07-14 00:43:06 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,594,411 · 13 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
2w03w14w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xacb6de83…d893
0x34b655…2a6f
4 touches
1 conflict
0x62bd1793…0097
0x34b655…2a6f
4 touches
1 conflict
0x0804b2ba…8a77
0x34b655…2a6f
2 touches
0 conflicts
0x0e403c18…eac8
0x34b655…2a6f
2 touches
0 conflicts
0x199944d5…ab9f
0x34b655…2a6f
2 touches
0 conflicts
0x43bf7a92…bd86
0x34b655…2a6f
2 touches
0 conflicts
0x4c188934…158e
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity