← previous blocknext block →recent activity
Analyzing
Block #87,357,541
30 transactions · 19 stateful · 2026-07-12 22:18:08 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,357,541 · 30 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
2w03w14w211w013w114w215w016w018w119w120w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
6 touches
3 conflicts
0x57ce1c16…5ed8
0xd32edf…ff58
5 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity