← previous blocknext block →recent activity
Analyzing
Block #94,912,555
15 transactions · 13 stateful · 2026-08-10 23:59:09 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,912,555 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w28w09w110w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63606de7…859d
0x968279…9342
6 touches
3 conflicts
0x0d1b66e5…bf3e
0x968279…9342
6 touches
3 conflicts
0x63606de7…8596
0x968279…9342
6 touches
3 conflicts
0x63606de7…8597
0x968279…9342
6 touches
3 conflicts
0x63606de7…859a
0x968279…9342
6 touches
3 conflicts
0x63606de7…859b
0x968279…9342
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
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: 0x96827978…f09342
3 conflicts on slot 0x63606de7e7…2c859d
Audit this contract →
← previous block·next block →recent activity