← previous blocknext block →recent activity
Analyzing
Block #94,848,369
12 transactions · 12 stateful · 2026-08-10 18:36:21 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,848,369 · 12 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
1w05w06w17w28w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8d6f3f5…5e4e
0x968279…9342
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0xda9f9d0c…25cc
0x968279…9342
6 touches
3 conflicts
0xda9f9d0c…25cd
0x968279…9342
6 touches
3 conflicts
0xda9f9d0c…25cf
0x968279…9342
6 touches
3 conflicts
0xe8d6f3f5…5e48
0x968279…9342
6 touches
3 conflicts
0xe8d6f3f5…5e49
0x968279…9342
6 touches
3 conflicts
0xe8d6f3f5…5e4c
0x968279…9342
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 0xe8d6f3f51e…ae5e4e
Audit this contract →
← previous block·next block →recent activity