← previous blocknext block →recent activity
Analyzing
Block #90,678,183
24 transactions · 23 stateful · 2026-07-27 04:37:57 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,678,183 · 24 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
2w04w05w16w27w38w411w012w114w215w116w218w321w122w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd43be87…f667
0xe1c8b7…3022
10 touches
10 conflicts
0x4eb758b8…b13b
0x3bd359…433a
10 touches
10 conflicts
0xc6101b5d…4361
0x3bd359…433a
10 touches
10 conflicts
0x5504f74a…6874
0x43cf54…7777
10 touches
10 conflicts
0x00000000…0004
0x48c3bb…b17b
10 touches
10 conflicts
0xa164d951…1534
0xe1c8b7…3022
10 touches
10 conflicts
0x44ed742f…63f5
0x3bd359…433a
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
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: 0xe1c8b733…e33022
10 conflicts on slot 0xdd43be87b3…92f667
Audit this contract →
← previous block·next block →recent activity