← previous blocknext block →recent activity
Analyzing
Block #90,288,436
19 transactions · 18 stateful · 2026-07-25 19:43:31 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,288,436 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w18w211w212w315w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe3471350…0bcf
0x34b655…2a6f
6 touches
3 conflicts
0x7c1d804e…835c
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbc2d4622…e7e9
0x34b655…2a6f
4 touches
1 conflict
0xc30234e3…c8fe
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 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity