← previous blocknext block →recent activity
Analyzing
Block #93,663,959
14 transactions · 13 stateful · 2026-08-06 15:01:49 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,663,959 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x1962b6a7…8526
0x851145…3f07
4 touches
1 conflict
0x5922c26d…3312
0x851145…3f07
4 touches
1 conflict
0xb8180e6d…17f3
0x851145…3f07
4 touches
1 conflict
0x8649e48f…941c
0xc8689a…ee79
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xf7640726…19a2
0x2a68ba…90c5
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity