← previous blocknext block →recent activity
Analyzing
Block #94,797,012
16 transactions · 15 stateful · 2026-08-10 14:17:58 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,797,012 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabd0bcfc…64e2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x0ec7fb56…bca1
0x34b655…2a6f
2 touches
0 conflicts
0x206186c0…5ba4
0x34b655…2a6f
2 touches
0 conflicts
0x746b3fc2…0b34
0x34b655…2a6f
2 touches
0 conflicts
0x793b6cb1…63c7
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0xabd0bcfc80…a364e2
Audit this contract →
← previous block·next block →recent activity