← previous blocknext block →recent activity
Analyzing
Block #100,870,974
35 transactions · 25 stateful · 2026-08-31 22:07:11 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,870,974 · 35 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w29w310w011w112w213w324w025w126w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x1d9154e7…8821
0x34b655…2a6f
4 touches
1 conflict
0xa03832a9…e262
0x34b655…2a6f
4 touches
1 conflict
0x55510089…d705
0x065c9d…c394
3 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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity