← previous blocknext block →recent activity
Analyzing
Block #90,992,859
30 transactions · 27 stateful · 2026-07-28 07:01:13 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,992,859 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w29w310w011w412w013w114w215w318w119w024w125w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x10c3012b…e952
0x34b655…2a6f
4 touches
1 conflict
0x13e48150…061f
0x34b655…2a6f
4 touches
1 conflict
0x20317244…edb4
0x34b655…2a6f
4 touches
1 conflict
0x2cc85280…c2f7
0x34b655…2a6f
4 touches
1 conflict
0x4f89e431…499f
0x34b655…2a6f
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: 0x48cba278…e2b48b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity