← previous blocknext block →recent activity
Analyzing
Block #90,637,318
18 transactions · 17 stateful · 2026-07-27 01:12:22 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,637,318 · 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
1w02w14w05w16w07w18w09w110w011w012w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe870e232…7369
0xf9b0c8…8081
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: 0xf9b0c8ee…ea8081
1 conflict on slot 0xe870e2326a…1a7369
Audit this contract →
← previous block·next block →recent activity