← previous blocknext block →recent activity
Analyzing
Block #87,350,710
16 transactions · 15 stateful · 2026-07-12 21:32:28 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,350,710 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w010w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d84bebc…07d1
0x34b655…2a6f
4 touches
1 conflict
0x3cef6445…87da
0x34b655…2a6f
4 touches
1 conflict
0x55c2c22c…0474
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d0
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
1 conflict on slot 0x1d84bebc66…b107d1
Audit this contract →
← previous block·next block →recent activity