← previous blocknext block →recent activity
Analyzing
Block #87,704,430
34 transactions · 22 stateful · 2026-07-14 12:58:44 UTC
Parallelism
85/100
Blocked
45%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,704,430 · 34 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
3w04w16w219w020w121w222w323w425w226w027w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x767799cd…f423
0xc8689a…ee79
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa57576bb…e01f
0x34b655…2a6f
6 touches
3 conflicts
0xb02dc238…2fca
0x34b655…2a6f
6 touches
3 conflicts
0xc5031114…58ac
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity