← previous blocknext block →recent activity
Analyzing
Block #94,953,374
19 transactions · 18 stateful · 2026-08-11 03:24:28 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,953,374 · 19 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
1w02w03w14w05w17w28w09w110w211w312w413w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c98f2fe…e3b8
0x968279…9342
10 touches
10 conflicts
0x1c98f2fe…e3b9
0x968279…9342
10 touches
10 conflicts
0x6bab8831…4337
0x968279…9342
10 touches
10 conflicts
0x1c98f2fe…e3b3
0x968279…9342
10 touches
10 conflicts
0x1c98f2fe…e3b4
0x968279…9342
10 touches
10 conflicts
0x1c98f2fe…e3b7
0x968279…9342
10 touches
10 conflicts
0x6bab8831…4336
0x968279…9342
10 touches
10 conflicts
0x6bab8831…4339
0x968279…9342
10 touches
10 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
10 conflicts on slot 0x1c98f2fe3b…11e3b8
Audit this contract →
← previous block·next block →recent activity