← previous blocknext block →recent activity
Analyzing
Block #87,643,123
20 transactions · 18 stateful · 2026-07-14 06:08:48 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,643,123 · 20 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
6w07w18w29w312w413w514w317w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
6 touches
3 conflicts
0x42c7fd6d…fc6c
0x34b655…2a6f
6 touches
3 conflicts
0x42aad825…b067
0x34b655…2a6f
4 touches
1 conflict
0x605ef416…dd46
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
10 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity