← previous blocknext block →recent activity
Analyzing
Block #87,312,758
16 transactions · 15 stateful · 2026-07-12 17:18:42 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,312,758 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w29w210w012w113w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa05444cf…cd70
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x3ed31132…62b6
0x34b655…2a6f
4 touches
1 conflict
0x3ef0952c…762d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50e84e6c…287f
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 0xa05444cff4…1ecd70
Audit this contract →
← previous block·next block →recent activity