← previous blocknext block →recent activity
Analyzing
Block #90,629,652
16 transactions · 15 stateful · 2026-07-27 00:33:48 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,629,652 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w214w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe068f0d8…ac71
0x34b655…2a6f
4 touches
1 conflict
0xe7c6b5b9…b03c
0x34b655…2a6f
4 touches
1 conflict
0xf9ac650a…d82d
0x34b655…2a6f
4 touches
1 conflict
0xfc3d5171…8357
0x34b655…2a6f
4 touches
1 conflict
0x2827cf71…013b
0x34b655…2a6f
4 touches
1 conflict
0x24eaf46d…8c2e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48e3acd8…cf41
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
1 conflict on slot 0xe068f0d8f8…1dac71
Audit this contract →
← previous block·next block →recent activity