← previous blocknext block →recent activity
Analyzing
Block #87,592,927
30 transactions · 24 stateful · 2026-07-14 00:33:11 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,592,927 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w19w010w211w312w413w515w021w124w228w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x167de262…f61f
0x34b655…2a6f
10 touches
10 conflicts
0x34d95d94…3a16
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd11dcf4e…518f
0x34b655…2a6f
10 touches
10 conflicts
0xd19c9d38…b459
0x34b655…2a6f
10 touches
10 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
8 touches
6 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 0x167de262c8…3ef61f
Audit this contract →
← previous block·next block →recent activity