← previous blocknext block →recent activity
Analyzing
Block #100,093,419
43 transactions · 37 stateful · 2026-08-29 04:50:39 UTC
Parallelism
74/100
Blocked
70%
Avg conflicts / tx
2.65
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,093,419 · 43 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w610w729w132w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0x3715640e…d6f7
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xba38536d…2b7d
0x065c9d…c394
10 touches
10 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: 0xf5b5f7f8…a36d70
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity