← previous blocknext block →recent activity
Analyzing
Block #90,679,688
36 transactions · 32 stateful · 2026-07-27 04:45:31 UTC
Parallelism
64/100
Blocked
78%
Avg conflicts / tx
2.06
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #90,679,688 · 36 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w17w08w19w211w012w113w214w015w116w217w318w419w520w422w523w225w326w427w229w632w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x65d2bd64…8afc
0x34b655…2a6f
8 touches
6 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4aa7bc6e…96f3
0x34b655…2a6f
6 touches
3 conflicts
0x7032dc14…49ea
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity