← previous blocknext block →recent activity
Analyzing
Block #100,103,266
16 transactions · 14 stateful · 2026-08-29 05:40:13 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,103,266 · 16 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
6w07w19w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5508b633…5bc3
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x5508b633…5bbe
0x8964d7…10f8
4 touches
1 conflict
0x5508b633…5bbf
0x8964d7…10f8
4 touches
1 conflict
0x5508b633…5bc2
0x8964d7…10f8
4 touches
1 conflict
0x51cfbcbc…fa29
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x5508b63323…a45bc3
Audit this contract →
← previous block·next block →recent activity