← previous blocknext block →recent activity
Analyzing
Block #89,570,107
18 transactions · 16 stateful · 2026-07-23 04:56:31 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,570,107 · 18 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
1w02w13w04w15w28w010w111w113w014w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x272b4272…2e3d
0x0a2fbf…29b1
4 touches
1 conflict
0x272b4272…2e3e
0x0a2fbf…29b1
4 touches
1 conflict
0x272b4272…2e41
0x0a2fbf…29b1
4 touches
1 conflict
0x75ba1ac0…2c20
0x0a2fbf…29b1
4 touches
1 conflict
0x75ba1ac0…2c21
0x0a2fbf…29b1
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity