← previous blocknext block →recent activity
Analyzing
Block #89,837,907
13 transactions · 13 stateful · 2026-07-24 05:50:25 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,837,907 · 13 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
1w02w14w05w16w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a628ea8…5918
0x851145…3f07
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5a100ac0…96d3
0x34b655…2a6f
4 touches
1 conflict
0x6faf12dc…7de7
0x34b655…2a6f
4 touches
1 conflict
0xac5cfb4e…bb6e
0x34b655…2a6f
4 touches
1 conflict
0xbd9491f7…dd92
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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: 0x851145ea…9f3f07
1 conflict on slot 0x2a628ea850…7c5918
Audit this contract →
← previous block·next block →recent activity