← previous blocknext block →recent activity
Analyzing
Block #100,226,852
8 transactions · 7 stateful · 2026-08-29 16:02:32 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,226,852 · 8 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
3w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fb8d71e…c267
0x8964d7…10f8
6 touches
3 conflicts
0x0fb8d71e…c268
0x8964d7…10f8
6 touches
3 conflicts
0x0fb8d71e…c26b
0x8964d7…10f8
6 touches
3 conflicts
0x0fb8d71e…c26c
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x0fb8d71e…c26d
0x8964d7…10f8
4 touches
1 conflict
0x31239739…cc75
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 0x0fb8d71ec8…38c267
Audit this contract →
← previous block·next block →recent activity