← previous blocknext block →recent activity
Analyzing
Block #100,869,864
13 transactions · 10 stateful · 2026-08-31 22:01:36 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,869,864 · 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
1w02w14w28w09w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa605468c…1bfc
0x34ae4d…3fc5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x06e40499…165e
0x34ae4d…3fc5
6 touches
3 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: 0x34ae4d08…a73fc5
3 conflicts on slot 0xa605468c6d…6d1bfc
Audit this contract →
← previous block·next block →recent activity