← previous blocknext block →recent activity
Analyzing
Block #90,394,443
14 transactions · 14 stateful · 2026-07-26 04:45:15 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,394,443 · 14 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
1w05w17w211w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac5cfb4e…bb6e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
4 touches
1 conflict
0x3055b4d0…81c0
0x34b655…2a6f
4 touches
1 conflict
0x380539e8…67a5
0x34b655…2a6f
4 touches
1 conflict
0x5018f751…0794
0x34b655…2a6f
4 touches
1 conflict
0x66df1715…26d1
0x34b655…2a6f
4 touches
1 conflict
0x74dae4f2…f2d8
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: Perpl
3 conflicts on slot 0xac5cfb4e33…acbb6e
Audit this contract →
← previous block·next block →recent activity