← previous blocknext block →recent activity
Analyzing
Block #100,249,608
14 transactions · 14 stateful · 2026-08-29 17:57:48 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,249,608 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w08w19w210w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9daa51f5…3da9
0x928dc8…8207
6 touches
3 conflicts
0x5311f864…0984
0x754704…b603
6 touches
3 conflicts
0x9daa51f5…3da5
0x928dc8…8207
4 touches
1 conflict
0x9daa51f5…3da8
0x928dc8…8207
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: 0x928dc8af…fd8207
3 conflicts on slot 0x9daa51f56d…d73da9
Audit this contract →
← previous block·next block →recent activity