← previous blocknext block →recent activity
Analyzing
Block #87,703,426
24 transactions · 23 stateful · 2026-07-14 12:51:59 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,703,426 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w29w010w111w215w018w119w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x55012d1a…3907
0x2b46c0…1669
4 touches
1 conflict
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0xb8fccd1b…b5f2
0x2b46c0…1669
4 touches
1 conflict
0x0090639e…243e
0x34b655…2a6f
4 touches
1 conflict
0x0c53719e…0366
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: 0xc1ff9fef…f4b0fc
3 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity