← previous blocknext block →recent activity
Analyzing
Block #100,049,933
13 transactions · 12 stateful · 2026-08-29 01:11:44 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,049,933 · 13 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
1w03w16w07w18w09w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7849f3a8…b807
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x7849f3a8…b800
0x8964d7…10f8
4 touches
1 conflict
0x7849f3a8…b801
0x8964d7…10f8
4 touches
1 conflict
0x7849f3a8…b804
0x8964d7…10f8
4 touches
1 conflict
0x7849f3a8…b805
0x8964d7…10f8
4 touches
1 conflict
0x61571888…b392
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
1 conflict on slot 0x7849f3a8be…dbb807
Audit this contract →
← previous block·next block →recent activity