← previous blocknext block →recent activity
Analyzing
Block #87,761,763
25 transactions · 23 stateful · 2026-07-14 19:22:26 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,761,763 · 25 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
2w03w16w010w112w213w316w017w118w222w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe23d5d8…cddd
0x34b655…2a6f
6 touches
3 conflicts
0xeb9b6ffc…3aab
0x34b655…2a6f
6 touches
3 conflicts
0xeb9b6ffc…3aac
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x896bf7d8…906b
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 0xbe23d5d818…c1cddd
Audit this contract →
← previous block·next block →recent activity