← previous blocknext block →recent activity
Analyzing
Block #87,258,365
14 transactions · 14 stateful · 2026-07-12 11:15:04 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,258,365 · 14 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
3w05w06w17w19w211w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0x04702c9b…1d9c
0x34b655…2a6f
4 touches
1 conflict
0x0477ecbb…dd4f
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x16ba1d53…4480
0x34b655…2a6f
4 touches
1 conflict
0x23ea6729…10b6
0x34b655…2a6f
4 touches
1 conflict
0x539bd236…90d1
0x34b655…2a6f
4 touches
1 conflict
0x78e07514…9fcc
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 0x006c3b8659…7a59a9
Audit this contract →
← previous block·next block →recent activity