← previous blocknext block →recent activity
Analyzing
Block #90,513,066
12 transactions · 11 stateful · 2026-07-26 14:47:19 UTC
Parallelism
75/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,513,066 · 12 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
6w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ee667a1…2a60
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x34a2c248…f7ed
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0002
0x48cba2…b48b
2 touches
0 conflicts
0x5311f864…0984
0x754704…b603
2 touches
0 conflicts
0x191e9889…fc9a
0x928dc8…8207
2 touches
0 conflicts
0x3e3e98af…206f
0x928dc8…8207
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
1 conflict on slot 0x5ee667a109…d62a60
Audit this contract →
← previous block·next block →recent activity