← previous blocknext block →recent activity
Analyzing
Block #90,992,404
5 transactions · 5 stateful · 2026-07-28 06:58:55 UTC
Parallelism
40/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,992,404 · 5 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x44b918e8…94d7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2e960d17…eb4c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x7182a94f…dc78
0x34b655…2a6f
4 touches
1 conflict
0x871707b3…21b1
0x34b655…2a6f
3 touches
1 conflict
0xc6afa1f2…ea19
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity