← previous blocknext block →recent activity
Analyzing
Block #87,666,726
20 transactions · 16 stateful · 2026-07-14 08:46:30 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,666,726 · 20 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
1w08w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24d68cf2…09b7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xfe4e62b8…9ade
0x34b655…2a6f
4 touches
1 conflict
0x042c98e4…2c39
0x34b655…2a6f
2 touches
0 conflicts
0x08e17950…ed0f
0x34b655…2a6f
2 touches
0 conflicts
0x099dde1a…3e64
0x34b655…2a6f
2 touches
0 conflicts
0x0bbc16ce…501b
0x34b655…2a6f
2 touches
0 conflicts
0x0caba47a…5357
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 0x24d68cf28e…9209b7
Audit this contract →
← previous block·next block →recent activity