← previous blocknext block →recent activity
Analyzing
Block #94,761,005
19 transactions · 19 stateful · 2026-08-10 11:16:51 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,761,005 · 19 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
1w02w13w05w19w211w312w414w517w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc2413c7…b4c2
0x34b655…2a6f
10 touches
10 conflicts
0xf3383813…4a0c
0x34b655…2a6f
10 touches
10 conflicts
0x28d74e20…c54e
0x34b655…2a6f
4 touches
1 conflict
0x35c29640…8779
0x34b655…2a6f
4 touches
1 conflict
0x38badd90…a68c
0x34b655…2a6f
4 touches
1 conflict
0x46822f8c…d048
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x671560e4…1c4f
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 0xbc2413c73a…7eb4c2
Audit this contract →
← previous block·next block →recent activity