← previous blocknext block →recent activity
Analyzing
Block #100,602,024
16 transactions · 12 stateful · 2026-08-30 23:33:52 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,602,024 · 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
1w02w14w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0xacb361c1…ad37
0x8964d7…10f8
6 touches
3 conflicts
0xacb361c1…ad38
0x8964d7…10f8
6 touches
3 conflicts
0xacb361c1…ad34
0x8964d7…10f8
6 touches
3 conflicts
0xacb361c1…ad33
0x8964d7…10f8
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity