← previous blocknext block →recent activity
Analyzing
Block #87,918,984
32 transactions · 25 stateful · 2026-07-15 12:54:04 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,918,984 · 32 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
1w08w09w110w011w114w015w116w117w218w322w223w324w428w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xaba2bbbd…f44a
0x34b655…2a6f
6 touches
3 conflicts
0xc6e33caa…ec53
0x34b655…2a6f
6 touches
3 conflicts
0xe63a9ab2…a44f
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x4b2b1640…1bb8
0x34b655…2a6f
6 touches
3 conflicts
0x692a4122…76b8
0x350035…7777
4 touches
1 conflict
0xb7143610…adc4
0x3bd359…433a
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity