← previous blocknext block →recent activity
Analyzing
Block #100,852,933
33 transactions · 26 stateful · 2026-08-31 20:36:27 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,852,933 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w28w316w020w122w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xf8c9546a…ebba
0x34b655…2a6f
4 touches
1 conflict
0xaa2e5b32…d93c
0x34b655…2a6f
4 touches
1 conflict
0x8bc5651b…6f4a
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
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: Perpl
3 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity