← previous blocknext block →recent activity
Analyzing
Block #87,661,721
19 transactions · 14 stateful · 2026-07-14 08:13:02 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,661,721 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w011w312w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xd69f26b4…c204
0x2a68ba…90c5
4 touches
1 conflict
0x54b13137…5bef
0x34b655…2a6f
4 touches
1 conflict
0x640530ff…86bc
0x34b655…2a6f
4 touches
1 conflict
0xf8ceaa24…6e8e
0x851145…3f07
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x7e5ea60a…c4aa
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity