← previous blocknext block →recent activity
Analyzing
Block #87,253,527
13 transactions · 12 stateful · 2026-07-12 10:42:39 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,253,527 · 13 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
4w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dc585ff…6c58
0x34b655…2a6f
4 touches
1 conflict
0x6c7b899c…70ff
0x34b655…2a6f
4 touches
1 conflict
0x6c7b899c…7100
0x34b655…2a6f
4 touches
1 conflict
0x7c11df38…2f2c
0x34b655…2a6f
4 touches
1 conflict
0x95794d9a…0de9
0x34b655…2a6f
4 touches
1 conflict
0xd72b1438…3cde
0x34b655…2a6f
4 touches
1 conflict
0xf1e0de4d…eb7f
0x34b655…2a6f
4 touches
1 conflict
0xb33ff823…1188
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 0x0dc585ff5d…286c58
Audit this contract →
← previous block·next block →recent activity