← previous blocknext block →recent activity
Analyzing
Block #93,920,936
21 transactions · 21 stateful · 2026-08-07 12:34:11 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,920,936 · 21 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
1w02w14w27w08w19w210w311w412w516w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2af0797b…397a
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0xf275b4ca…57b8
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0x41377979…0a18
0x34b655…2a6f
8 touches
6 conflicts
0xfa48b154…9988
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
15 conflicts on slot 0x2af0797b15…35397a
Audit this contract →
← previous block·next block →recent activity