← previous blocknext block →recent activity
Analyzing
Block #87,625,276
19 transactions · 17 stateful · 2026-07-14 04:09:30 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,625,276 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w28w09w111w312w413w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xee0cc1b7…de22
0x34b655…2a6f
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
6 touches
3 conflicts
0xd44615c6…5430
0x34b655…2a6f
6 touches
3 conflicts
0xcfcb8911…e9da
0x34b655…2a6f
4 touches
1 conflict
0xd97c2fdb…27d5
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity