← previous blocknext block →recent activity
Analyzing
Block #94,962,661
21 transactions · 19 stateful · 2026-08-11 04:11:10 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,962,661 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w19w010w111w112w217w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0xe41687e2…9dcb
0x065c9d…c394
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x11e1426c…0d03
0x34b655…2a6f
4 touches
1 conflict
0x1ffbc5c9…461f
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
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
10 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity