← previous blocknext block →recent activity
Analyzing
Block #88,139,071
22 transactions · 20 stateful · 2026-07-16 13:26:11 UTC
Parallelism
91/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,139,071 · 22 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
1w02w16w08w19w010w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
4 touches
1 conflict
0xa9b8a24d…3277
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x18dc3f96…0d05
0x34b655…2a6f
4 touches
1 conflict
0x6fb92ed4…7205
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 0x9465204cd8…debf37
Audit this contract →
← previous block·next block →recent activity