← previous blocknext block →recent activity
Analyzing
Block #90,067,037
16 transactions · 15 stateful · 2026-07-25 01:04:33 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,067,037 · 16 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
2w03w14w27w08w19w110w213w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x41ba3c28…d76b
0x34b655…2a6f
4 touches
1 conflict
0x47dff289…3e6a
0x34b655…2a6f
4 touches
1 conflict
0x5d77346a…863a
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity