← previous blocknext block →recent activity
Analyzing
Block #94,720,586
10 transactions · 8 stateful · 2026-08-10 07:52:04 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,720,586 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c16527f…628c
0x34b655…2a6f
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ccfbdee…3731
0x34b655…2a6f
2 touches
0 conflicts
0x3230413b…bc7f
0x34b655…2a6f
2 touches
0 conflicts
0x41377979…0a18
0x34b655…2a6f
2 touches
0 conflicts
0x6f5e7a23…6c6f
0x34b655…2a6f
2 touches
0 conflicts
0x74e63d51…07ab
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
6 conflicts on slot 0x5c16527f85…5b628c
Audit this contract →
← previous block·next block →recent activity