← previous blocknext block →recent activity
Analyzing
Block #90,616,267
17 transactions · 15 stateful · 2026-07-26 23:26:28 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,616,267 · 17 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
2w03w14w25w36w27w310w411w513w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c0d73d9…04b8
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
6 conflicts on slot 0x1c0d73d9dd…fe04b8
Audit this contract →
← previous block·next block →recent activity