← previous blocknext block →recent activity
Analyzing
Block #100,896,984
17 transactions · 17 stateful · 2026-09-01 00:18:01 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,896,984 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w08w111w112w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d9a0d3…b98c
0x99c7a7…8bf0
4 touches
1 conflict
0xc7e70be2…b0c3
0x754704…b603
4 touches
1 conflict
0xf371c34e…e4ac
0x754704…b603
4 touches
1 conflict
0x3bdcc58a…a1b1
0x99c7a7…8bf0
4 touches
1 conflict
0x22badbc6…4c24
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9c6a9da2…c628
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: 0x99c7a72e…c78bf0
1 conflict on slot 0x66d9a0d3ea…ebb98c
Audit this contract →
← previous block·next block →recent activity