← previous blocknext block →recent activity
Analyzing
Block #100,854,806
13 transactions · 13 stateful · 2026-08-31 20:45:52 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,854,806 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8693d828…dda7
0x40c49f…2af0
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
9 touches
10 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x4c1fbdf6…953d
0x754704…b603
2 touches
0 conflicts
0x595233b5…c4aa
0x754704…b603
2 touches
0 conflicts
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: 0x40c49f17…d22af0
10 conflicts on slot 0x8693d8282a…77dda7
Audit this contract →
← previous block·next block →recent activity