← previous blocknext block →recent activity
Analyzing
Block #89,542,297
16 transactions · 14 stateful · 2026-07-23 01:50:42 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,542,297 · 16 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
3w07w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd514a7ae…1e04
0x34b655…2a6f
3 touches
1 conflict
0xffcf7999…0134
0x34b655…2a6f
3 touches
1 conflict
0x1d073c26…c9f6
0x57ea24…2cec
2 touches
0 conflicts
0x359ea8c7…4589
0x57ea24…2cec
2 touches
0 conflicts
0x451f0c72…64f0
0x57ea24…2cec
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 0x9e70dadd35…1b810d
Audit this contract →
← previous block·next block →recent activity