← previous blocknext block →recent activity
Analyzing
Block #87,340,814
7 transactions · 6 stateful · 2026-07-12 20:26:20 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,340,814 · 7 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x387231f6…6b29
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xf0d9d32a…dc4d
0x34b655…2a6f
4 touches
1 conflict
0x626831c3…246d
0x34b655…2a6f
2 touches
0 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
2 touches
0 conflicts
0x680ca7d7…2df4
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 0x387231f636…416b29
Audit this contract →
← previous block·next block →recent activity