← previous blocknext block →recent activity
Analyzing
Block #100,583,242
19 transactions · 19 stateful · 2026-08-30 21:59:23 UTC
Parallelism
84/100
Blocked
16%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,583,242 · 19 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
1w03w05w17w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf20e3c30…c1be
0x40c49f…2af0
4 touches
1 conflict
0x0b10f1de…fc43
0x34b655…2a6f
4 touches
1 conflict
0x10bda07c…fd01
0x34b655…2a6f
4 touches
1 conflict
0x8c6a35cc…79f4
0x34b655…2a6f
4 touches
1 conflict
0xb51a7ce8…5102
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0xf20e3c3054…97c1be
Audit this contract →
← previous block·next block →recent activity