← previous blocknext block →recent activity
Analyzing
Block #100,925,306
18 transactions · 17 stateful · 2026-09-01 02:40:29 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,925,306 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w08w111w012w114w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc45ff9a4…2a95
0x40c49f…2af0
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xdc9915b5…542c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x0ec96a42…2743
0x40c49f…2af0
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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: 0x40c49f17…d22af0
1 conflict on slot 0xc45ff9a43f…4a2a95
Audit this contract →
← previous block·next block →recent activity