← previous blocknext block →recent activity
Analyzing
Block #93,344,429
28 transactions · 23 stateful · 2026-08-05 12:15:26 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,344,429 · 28 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
2w03w14w09w010w111w012w215w116w117w219w220w321w422w525w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x1803586e…d149
0xa6afd3…d132
8 touches
6 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0xa1a51db3…eba8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0xca841faa…486a
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity