← previous blocknext block →recent activity
Analyzing
Block #100,722,964
16 transactions · 12 stateful · 2026-08-31 09:42:14 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,722,964 · 16 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
9w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf502e4d6…a23a
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0xf502e4d6…a233
0x8964d7…10f8
6 touches
3 conflicts
0xf502e4d6…a234
0x8964d7…10f8
6 touches
3 conflicts
0xf502e4d6…a237
0x8964d7…10f8
6 touches
3 conflicts
0xf502e4d6…a238
0x8964d7…10f8
6 touches
3 conflicts
0x0d1814e1…16a4
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
3 conflicts on slot 0xf502e4d687…7ea23a
Audit this contract →
← previous block·next block →recent activity