← previous blocknext block →recent activity
Analyzing
Block #100,225,712
14 transactions · 14 stateful · 2026-08-29 15:56:47 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,225,712 · 14 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
1w02w15w27w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x27b6010e…e4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x08ff2573…8168
0x34b655…2a6f
2 touches
0 conflicts
0x38befc08…20c8
0x34b655…2a6f
2 touches
0 conflicts
0x4be9812b…48a9
0x34b655…2a6f
2 touches
0 conflicts
0x5684aadd…8d62
0x34b655…2a6f
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity