← previous blocknext block →recent activity
Analyzing
Block #100,868,964
21 transactions · 18 stateful · 2026-08-31 21:57:05 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,868,964 · 21 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
3w04w15w27w08w111w112w213w315w016w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c455afd…ce06
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x049d1b67…90b0
0x928dc8…8207
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x497d19bc…865e
0x34b655…2a6f
4 touches
1 conflict
0xc96678e0…6a10
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
6 conflicts on slot 0x5c455afdfc…27ce06
Audit this contract →
← previous block·next block →recent activity