← previous blocknext block →recent activity
Analyzing
Block #100,925,821
14 transactions · 11 stateful · 2026-09-01 02:43:04 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,925,821 · 14 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
1w02w14w05w111w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71fad9ce…c11f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2f763e0d…7b5e
0x065c9d…c394
2 touches
0 conflicts
0x33dea0e7…88c8
0x065c9d…c394
2 touches
0 conflicts
0x4dd02c13…2e52
0x065c9d…c394
2 touches
0 conflicts
0xc69c92e7…2762
0x065c9d…c394
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: Perpl
3 conflicts on slot 0x71fad9ce4b…8ac11f
Audit this contract →
← previous block·next block →recent activity