← previous blocknext block →recent activity
Analyzing
Block #94,967,514
14 transactions · 13 stateful · 2026-08-11 04:35:35 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,967,514 · 14 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
1w02w15w06w17w28w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1bc79ff…98a5
0x968279…9342
6 touches
3 conflicts
0x929f2b6c…f11c
0x968279…9342
6 touches
3 conflicts
0xd1bc79ff…989e
0x968279…9342
6 touches
3 conflicts
0xd1bc79ff…989f
0x968279…9342
6 touches
3 conflicts
0xd1bc79ff…98a2
0x968279…9342
6 touches
3 conflicts
0xd1bc79ff…98a3
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 0xd1bc79ff25…4698a5
Audit this contract →
← previous block·next block →recent activity