← previous blocknext block →recent activity
Analyzing
Block #94,839,135
14 transactions · 14 stateful · 2026-08-10 17:49:53 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,839,135 · 14 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
1w02w16w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd42c0a7f…ece1
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0x6cc5ca07…1020
0xe52b14…7230
10 touches
10 conflicts
0xd42c0a7f…ecdf
0xe52b14…7230
10 touches
10 conflicts
0xe95e0abf…8bdc
0xe52b14…7230
8 touches
10 conflicts
0x6cc5ca07…1022
0xe52b14…7230
8 touches
6 conflicts
0xb32ee1d3…3a44
0xe52b14…7230
5 touches
3 conflicts
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 0xd42c0a7f23…71ece1
Audit this contract →
← previous block·next block →recent activity