← previous blocknext block →recent activity
Analyzing
Block #100,154,283
14 transactions · 14 stateful · 2026-08-29 09:57:14 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,154,283 · 14 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
5w08w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee08336…7811
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x7ee08336…780a
0x8964d7…10f8
6 touches
3 conflicts
0x7ee08336…780b
0x8964d7…10f8
6 touches
3 conflicts
0x7ee08336…780e
0x8964d7…10f8
6 touches
3 conflicts
0x7ee08336…780f
0x8964d7…10f8
6 touches
3 conflicts
0xd2e4fc81…163c
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
3 conflicts on slot 0x7ee0833611…b57811
Audit this contract →
← previous block·next block →recent activity