← previous blocknext block →recent activity
Analyzing
Block #94,810,846
13 transactions · 13 stateful · 2026-08-10 15:27:34 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,810,846 · 13 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfed09e59…a493
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01dc29d8…bcd2
0x34b655…2a6f
2 touches
0 conflicts
0x0bc506f8…92a2
0x34b655…2a6f
2 touches
0 conflicts
0x0e2c8224…e84b
0x34b655…2a6f
2 touches
0 conflicts
0x1416e2fb…e2b3
0x34b655…2a6f
2 touches
0 conflicts
0x1c3ae63a…7566
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 0xfed09e59c7…d6a493
Audit this contract →
← previous block·next block →recent activity