← previous blocknext block →recent activity
Analyzing
Block #87,346,588
14 transactions · 12 stateful · 2026-07-12 21:04:55 UTC
Parallelism
57/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,346,588 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4e5e0c2…6e04
0x34b655…2a6f
6 touches
3 conflicts
0xbc94dfe1…0b3d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x680ca7d7…2df4
0x34b655…2a6f
4 touches
1 conflict
0x7634a3f4…7f24
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
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
3 conflicts on slot 0xa4e5e0c2c4…d76e04
Audit this contract →
← previous block·next block →recent activity