← previous blocknext block →recent activity
Analyzing
Block #87,410,438
16 transactions · 16 stateful · 2026-07-13 04:12:02 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,410,438 · 16 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
1w02w13w25w210w311w012w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x086db8fc…0024
0x34b655…2a6f
6 touches
3 conflicts
0x801058a8…5bc3
0x34b655…2a6f
6 touches
3 conflicts
0x003efbe8…2c31
0x34b655…2a6f
4 touches
1 conflict
0x05a7428b…ddf3
0x34b655…2a6f
4 touches
1 conflict
0x77a99df7…d784
0x851145…3f07
4 touches
1 conflict
0xd69f26b4…c204
0x2a68ba…90c5
4 touches
1 conflict
0xdbc62196…3245
0x34b655…2a6f
4 touches
1 conflict
0xe27242f5…0a76
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 0x086db8fc6e…830024
Audit this contract →
← previous block·next block →recent activity