← previous blocknext block →recent activity
Analyzing
Block #94,953,354
14 transactions · 12 stateful · 2026-08-11 03:24:22 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,953,354 · 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
5w06w17w08w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x6bab8831…4339
0x968279…9342
4 touches
1 conflict
0x1c98f2fe…e3b7
0x968279…9342
4 touches
1 conflict
0x1c98f2fe…e3b8
0x968279…9342
4 touches
1 conflict
0x1c98f2fe…e3b9
0x968279…9342
4 touches
1 conflict
0x6bab8831…4336
0x968279…9342
4 touches
1 conflict
0x6bab8831…4337
0x968279…9342
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: Perpl
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity