← previous blocknext block →recent activity
Analyzing
Block #94,815,468
12 transactions · 12 stateful · 2026-08-10 15:50:49 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,815,468 · 12 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
1w05w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c200611…8d6b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb5924647…4cf1
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x697a3697…077c
0x34b655…2a6f
2 touches
0 conflicts
0x73dfcba5…1873
0x34b655…2a6f
2 touches
0 conflicts
0x7df11bd9…ae75
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 0x7c200611b4…ac8d6b
Audit this contract →
← previous block·next block →recent activity