← previous blocknext block →recent activity
Analyzing
Block #90,387,190
15 transactions · 14 stateful · 2026-07-26 04:07:57 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,387,190 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w17w39w411w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2ffa1f3…d3ae
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc73549e8…2001
0x34b655…2a6f
6 touches
3 conflicts
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x4af8f8d2…0850
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xd2ffa1f3c7…48d3ae
Audit this contract →
← previous block·next block →recent activity