← previous blocknext block →recent activity
Analyzing
Block #87,441,082
12 transactions · 11 stateful · 2026-07-13 07:36:50 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,441,082 · 12 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
1w02w13w04w15w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0aaad90…2698
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x9ee338ef…ab21
0x34b655…2a6f
4 touches
1 conflict
0xc37a29e6…4d88
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc8c78f09…723b
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0xf0aaad90…2697
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 0xf0aaad909b…a52698
Audit this contract →
← previous block·next block →recent activity