← previous blocknext block →recent activity
Analyzing
Block #87,333,417
19 transactions · 18 stateful · 2026-07-12 19:36:53 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,333,417 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w112w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x2f6e3f9b…cced
0x3c2269…cf62
2 touches
0 conflicts
0x577b2428…6cab
0x3c2269…cf62
2 touches
0 conflicts
0x7a814f0d…35fd
0x3c2269…cf62
2 touches
0 conflicts
0xd2fc21b0…f410
0x3c2269…cf62
2 touches
0 conflicts
0xd4cd1c4d…6ae2
0x3c2269…cf62
2 touches
0 conflicts
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity