← previous blocknext block →recent activity
Analyzing
Block #87,712,042
21 transactions · 19 stateful · 2026-07-14 13:49:42 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,712,042 · 21 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
1w03w04w18w011w112w213w316w417w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d85c11e…9c54
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xded7831c…3c4a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x38b5b2ce…c5bb
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…00c9
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 0x6d85c11e6e…409c54
Audit this contract →
← previous block·next block →recent activity