← previous blocknext block →recent activity
Analyzing
Block #90,603,469
14 transactions · 13 stateful · 2026-07-26 22:22:04 UTC
Parallelism
50/100
Blocked
54%
Avg conflicts / tx
1.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,603,469 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w18w29w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x947f1921…b1ba
0x34b655…2a6f
6 touches
3 conflicts
0x7bc81c3e…54a2
0x34b655…2a6f
6 touches
3 conflicts
0x3e30f1bf…6453
0x34b655…2a6f
6 touches
3 conflicts
0xd0ff5982…26bc
0x34b655…2a6f
6 touches
3 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x3deaaafc…fa93
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity