← previous blocknext block →recent activity
Analyzing
Block #87,703,224
18 transactions · 18 stateful · 2026-07-14 12:50:37 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,703,224 · 18 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
5w06w07w114w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf094e5be…d695
0x34b655…2a6f
4 touches
1 conflict
0xc8536f01…eb88
0x34b655…2a6f
4 touches
1 conflict
0xc9337228…7eaf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1c1e591b…d93d
0x34b655…2a6f
4 touches
1 conflict
0x5c591136…d322
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 0xf094e5be0e…6ad695
Audit this contract →
← previous block·next block →recent activity