← previous blocknext block →recent activity
Analyzing
Block #94,720,859
10 transactions · 9 stateful · 2026-08-10 07:53:26 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,720,859 · 10 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
1w02w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x787e6b5e…3130
0x34b655…2a6f
4 touches
1 conflict
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0x5c16527f…628c
0x34b655…2a6f
4 touches
1 conflict
0x606cbae8…52c4
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x025fef2f…9738
0x34b655…2a6f
2 touches
0 conflicts
0x9f24d067…94eb
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 0x787e6b5e79…133130
Audit this contract →
← previous block·next block →recent activity