← previous blocknext block →recent activity
Analyzing
Block #87,350,266
13 transactions · 11 stateful · 2026-07-12 21:29:30 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,350,266 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d19b
0xb1dbf0…c0d3
4 touches
1 conflict
0x00000000…0004
0xb1dbf0…c0d3
4 touches
1 conflict
0x00cd9338…40d2
0x34b655…2a6f
4 touches
1 conflict
0x1f83b6db…8a0b
0x34b655…2a6f
4 touches
1 conflict
0x2b4f426d…5de5
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7b
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
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
1 conflict on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity