← previous blocknext block →recent activity
Analyzing
Block #87,753,409
33 transactions · 23 stateful · 2026-07-14 18:26:34 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,753,409 · 33 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
3w04w15w06w17w08w117w219w220w325w426w327w330w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x648bb928…97f2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x808aff35…5c6f
0x34b655…2a6f
6 touches
3 conflicts
0xa5deef6f…6c3f
0x34b655…2a6f
6 touches
3 conflicts
0xb125481e…4646
0x34b655…2a6f
6 touches
3 conflicts
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 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity