← previous blocknext block →recent activity
Analyzing
Block #94,683,820
13 transactions · 13 stateful · 2026-08-10 04:47:09 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,683,820 · 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
1w03w04w18w19w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8982aa7…cbbf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x57a45b1a…5229
0x34b655…2a6f
4 touches
1 conflict
0x6b329d79…f248
0x34b655…2a6f
4 touches
1 conflict
0xb550abea…2729
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
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
1 conflict on slot 0xf8982aa77c…f1cbbf
Audit this contract →
← previous block·next block →recent activity