← previous blocknext block →recent activity
Analyzing
Block #87,287,693
17 transactions · 13 stateful · 2026-07-12 14:31:08 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,287,693 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w08w19w010w112w213w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x74888025…a5b8
0x34b655…2a6f
4 touches
1 conflict
0x8b818135…eff8
0x34b655…2a6f
4 touches
1 conflict
0xb0b4210b…545e
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc8024fac…da0a
0x34b655…2a6f
4 touches
1 conflict
0xc8024fac…da0b
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity