← previous blocknext block →recent activity
Analyzing
Block #87,294,315
13 transactions · 12 stateful · 2026-07-12 15:15:26 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,294,315 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31876b09…a36e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x8eef368f…aa21
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa9df6131…bf9a
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc9dce17a…a1a1
0x34b655…2a6f
4 touches
1 conflict
0x259f3ba0…a139
0x34b655…2a6f
2 touches
0 conflicts
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 0x31876b09c6…8ea36e
Audit this contract →
← previous block·next block →recent activity