← previous blocknext block →recent activity
Analyzing
Block #100,750,958
25 transactions · 23 stateful · 2026-08-31 12:03:03 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,750,958 · 25 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
2w03w04w15w06w17w29w011w014w015w117w118w120w021w122w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x71ce1ca8…0460
0x851145…3f07
4 touches
1 conflict
0xf1cc56f9…384c
0x851145…3f07
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: 0xf5b5f7f8…a36d70
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity