← previous blocknext block →recent activity
Analyzing
Block #100,851,021
23 transactions · 22 stateful · 2026-08-31 20:26:50 UTC
Parallelism
78/100
Blocked
32%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,851,021 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w09w010w111w212w313w417w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77db3635…bd1f
0x40c49f…2af0
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x3e1e8e54…9c83
0x2a68ba…90c5
10 touches
10 conflicts
0x51cfbcbc…fa29
0x34b655…2a6f
6 touches
3 conflicts
0xf4b2a427…0234
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9288
0x34ae4d…3fc5
2 touches
0 conflicts
0xce1efe70…2ec8
0x34ae4d…3fc5
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: 0x40c49f17…d22af0
10 conflicts on slot 0x77db3635f7…7abd1f
Audit this contract →
← previous block·next block →recent activity