← previous blocknext block →recent activity
Analyzing
Block #87,419,300
23 transactions · 21 stateful · 2026-07-13 05:11:17 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,419,300 · 23 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
4w09w010w113w214w015w317w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19d0eecc…6863
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x8be39390…47fd
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xbb1e628e…41ec
0x34b655…2a6f
6 touches
3 conflicts
0x15b254ac…664f
0x34b655…2a6f
6 touches
3 conflicts
0x37ab49be…3b8b
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: Perpl
6 conflicts on slot 0x19d0eecc2d…d66863
Audit this contract →
← previous block·next block →recent activity