← previous blocknext block →recent activity
Analyzing
Block #87,919,092
30 transactions · 24 stateful · 2026-07-15 12:54:47 UTC
Parallelism
83/100
Blocked
54%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,919,092 · 30 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
1w02w13w24w35w06w17w08w19w210w311w020w121w222w325w227w428w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b374c44…96d9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc88f593e…5d93
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xb566cc65…214d
0xa6afd3…d132
6 touches
3 conflicts
0x47d4745e…02bb
0x336ed4…c59c
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 0x1b374c447e…d896d9
Audit this contract →
← previous block·next block →recent activity