← previous blocknext block →recent activity
Analyzing
Block #87,712,293
24 transactions · 21 stateful · 2026-07-14 13:51:22 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,712,293 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w010w011w112w213w314w415w517w518w119w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x35c429dc…0201
0x34b655…2a6f
4 touches
1 conflict
0x3eeca510…5146
0x34b655…2a6f
4 touches
1 conflict
0x4f1e16d4…4833
0x34b655…2a6f
4 touches
1 conflict
0x60d453fc…5968
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity