← previous blocknext block →recent activity
Analyzing
Block #89,549,163
18 transactions · 16 stateful · 2026-07-23 02:36:35 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,549,163 · 18 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
1w05w17w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55d78f9a…d50b
0x34b655…2a6f
4 touches
1 conflict
0x6e19c9a0…7d86
0x34b655…2a6f
4 touches
1 conflict
0xb900efa2…8624
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x2acb6edf…6b4f
0x34b655…2a6f
2 touches
0 conflicts
0x48203298…65cb
0x34b655…2a6f
2 touches
0 conflicts
0x4c572810…b89b
0x34b655…2a6f
2 touches
0 conflicts
0x53bda555…3810
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 0x55d78f9adb…0dd50b
Audit this contract →
← previous block·next block →recent activity