← previous blocknext block →recent activity
Analyzing
Block #100,141,675
16 transactions · 16 stateful · 2026-08-29 08:53:46 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,141,675 · 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
2w010w011w112w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae7b510c…9868
0x8964d7…10f8
4 touches
1 conflict
0x4fce7d8e…7b28
0x8964d7…10f8
4 touches
1 conflict
0x4fce7d8e…7b29
0x8964d7…10f8
4 touches
1 conflict
0x4fce7d8e…7b2c
0x8964d7…10f8
4 touches
1 conflict
0x4fce7d8e…7b2d
0x8964d7…10f8
4 touches
1 conflict
0x4fce7d8e…7b2e
0x8964d7…10f8
4 touches
1 conflict
0xae7b510c…9865
0x8964d7…10f8
4 touches
1 conflict
0xae7b510c…9866
0x8964d7…10f8
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 0xae7b510ce2…189868
Audit this contract →
← previous block·next block →recent activity