← previous blocknext block →recent activity
Analyzing
Block #87,614,259
30 transactions · 24 stateful · 2026-07-14 02:55:50 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,614,259 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w08w010w012w113w216w017w118w222w123w324w125w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3439dfbc…0d03
0x34b655…2a6f
8 touches
6 conflicts
0x0bce8fb9…edb6
0x34b655…2a6f
6 touches
3 conflicts
0x4f1e16d4…4833
0x34b655…2a6f
6 touches
3 conflicts
0xe8352ac7…d7a3
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x59a54ff4…d21b
0x34b655…2a6f
4 touches
1 conflict
0x59bfb0ed…ebd2
0x34b655…2a6f
4 touches
1 conflict
0x796c1a47…2bfb
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
6 conflicts on slot 0x3439dfbcc6…080d03
Audit this contract →
← previous block·next block →recent activity