← previous blocknext block →recent activity
Analyzing
Block #100,565,425
26 transactions · 22 stateful · 2026-08-30 20:29:45 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,565,425 · 26 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
2w04w15w26w07w08w19w010w114w215w316w419w524w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33000c0a…82c3
0x34b655…2a6f
10 touches
10 conflicts
0x38e9699c…50df
0x34b655…2a6f
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
4 touches
1 conflict
0x2b30a8fa…7e76
0x34b655…2a6f
4 touches
1 conflict
0x47b16af1…221e
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 0x33000c0a30…f582c3
Audit this contract →
← previous block·next block →recent activity