← previous blocknext block →recent activity
Analyzing
Block #87,360,434
17 transactions · 16 stateful · 2026-07-12 22:37:29 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,360,434 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w19w010w311w112w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9138a113…0d5f
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x24357e9f…b5cf
0x34b655…2a6f
6 touches
3 conflicts
0x472dd61b…64fe
0x34b655…2a6f
6 touches
3 conflicts
0x5379f516…8bf2
0x34b655…2a6f
6 touches
3 conflicts
0x5c8d9778…572f
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x9138a113b1…c30d5f
Audit this contract →
← previous block·next block →recent activity