← previous blocknext block →recent activity
Analyzing
Block #87,453,312
16 transactions · 13 stateful · 2026-07-13 08:58:39 UTC
Parallelism
56/100
Blocked
46%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,453,312 · 16 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
6w07w18w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xc36fa358…24cb
0x34b655…2a6f
12 touches
15 conflicts
0x239122db…dc81
0x34b655…2a6f
8 touches
6 conflicts
0x91ac6bd6…3754
0x34b655…2a6f
6 touches
3 conflicts
0x457cca76…23b0
0x34b655…2a6f
4 touches
1 conflict
0x4f772b19…5aeb
0x34b655…2a6f
4 touches
1 conflict
0x4faeec21…da80
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c55
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity