← previous blocknext block →recent activity
Analyzing
Block #87,615,281
23 transactions · 19 stateful · 2026-07-14 03:02:40 UTC
Parallelism
78/100
Blocked
37%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,615,281 · 23 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
1w02w05w17w213w216w117w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe197e523…ef9c
0x34b655…2a6f
6 touches
3 conflicts
0xc514314c…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0x1ebb35bb…ef2a
0x34b655…2a6f
4 touches
1 conflict
0x3ca9a061…1f41
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x6323c5ea…ce8a
0x34b655…2a6f
4 touches
1 conflict
0x6638e124…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x6b259aa9…cfba
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
3 conflicts on slot 0xe197e52366…87ef9c
Audit this contract →
← previous block·next block →recent activity