← previous blocknext block →recent activity
Analyzing
Block #107,823,884
27 transactions · 22 stateful · 2026-09-25 06:40:26 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,823,884 · 27 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
4w05w113w014w116w019w020w123w224w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9cb
0x508254…98bd
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3a663e9a…a9c8
0x508254…98bd
6 touches
3 conflicts
0x744dd823…909f
0x34b655…2a6f
4 touches
1 conflict
0xaf04b405…3599
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf51a94f0…f9b9
0x34b655…2a6f
4 touches
1 conflict
0x34a18f58…4c82
0x508254…98bd
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: 0x508254c8…4a98bd
3 conflicts on slot 0x3a663e9a3a…2fa9cb
Audit this contract →
← previous block·next block →recent activity