← previous blocknext block →recent activity
Analyzing
Block #87,441,696
12 transactions · 9 stateful · 2026-07-13 07:40:57 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,441,696 · 12 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
1w02w14w05w16w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c84762f…1cbe
0x34b655…2a6f
4 touches
1 conflict
0x2903260c…079c
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1c84762f…1cbd
0x34b655…2a6f
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xb922a263…e100
0x065c9d…c394
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 0x1c84762f24…da1cbe
Audit this contract →
← previous block·next block →recent activity