← previous blocknext block →recent activity
Analyzing
Block #87,046,029
31 transactions · 25 stateful · 2026-07-11 11:35:16 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,046,029 · 31 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
2w03w07w18w19w011w117w020w022w123w225w327w128w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x10722d1b…8a53
0x34b655…2a6f
6 touches
3 conflicts
0x1ced2a7d…5c90
0x34b655…2a6f
6 touches
3 conflicts
0x36638a70…343b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5a65207b…4f30
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…aaff
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 0x94ba9c4a07…0c41d8
Audit this contract →
← previous block·next block →recent activity