← previous blocknext block →recent activity
Analyzing
Block #93,923,256
22 transactions · 17 stateful · 2026-08-07 12:45:50 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,923,256 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w39w410w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30e
0xe52b14…7230
10 touches
10 conflicts
0x51232c8c…f30c
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xb19d0514…2125
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc2
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc0
0xe52b14…7230
10 touches
10 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
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: 0xe52b1424…bb7230
10 conflicts on slot 0x51232c8c1f…6df30e
Audit this contract →
← previous block·next block →recent activity