← previous blocknext block →recent activity
Analyzing
Block #90,916,349
11 transactions · 11 stateful · 2026-07-28 00:36:14 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,916,349 · 11 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
2w03w04w16w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcedd9c7b…916e
0x34b655…2a6f
6 touches
3 conflicts
0xf845b6ce…0547
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cbcf0b0…ad4c
0x34b655…2a6f
4 touches
1 conflict
0x602aaec2…5680
0x34b655…2a6f
4 touches
1 conflict
0x646278ac…2ebf
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xcedd9c7b7e…dc916e
Audit this contract →
← previous block·next block →recent activity