← previous blocknext block →recent activity
Analyzing
Block #89,759,462
38 transactions · 36 stateful · 2026-07-23 23:14:27 UTC
Parallelism
68/100
Blocked
72%
Avg conflicts / tx
3.18
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #89,759,462 · 38 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w310w011w112w213w314w015w016w117w218w119w320w421w222w523w624w325w726w828w929w430w1032w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
24 touches
66 conflicts
0x92339d95…0800
0x0000a8…8888
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2b96d534…b6b5
0x34b655…2a6f
6 touches
3 conflicts
0x5a2f19ef…f94e
0x34b655…2a6f
6 touches
3 conflicts
0x66adab49…dd90
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
6 touches
3 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: 0xb1c8ead4…c38888
66 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity