← previous blocknext block →recent activity
Analyzing
Block #93,878,901
18 transactions · 18 stateful · 2026-08-07 09:02:23 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,878,901 · 18 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
1w02w13w04w16w07w08w19w210w311w412w113w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf275b4ca…57b8
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc0
0xe52b14…7230
10 touches
10 conflicts
0x51232c8c…f30e
0xe52b14…7230
10 touches
10 conflicts
0x51232c8c…f30c
0xe52b14…7230
10 touches
10 conflicts
0x22cb82af…5b2b
0xe52b14…7230
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
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: 0xe52b1424…bb7230
10 conflicts on slot 0xf275b4ca84…5d57b8
Audit this contract →
← previous block·next block →recent activity