← previous blocknext block →recent activity
Analyzing
Block #100,634,047
24 transactions · 18 stateful · 2026-08-31 02:14:58 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,634,047 · 24 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
1w03w14w213w014w115w217w118w119w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x06d7243a…2d20
0x34ae4d…3fc5
4 touches
1 conflict
0x2a981bf0…9528
0x34ae4d…3fc5
4 touches
1 conflict
0x35813fea…f80d
0x34ae4d…3fc5
4 touches
1 conflict
0x3dca700c…13b1
0x34ae4d…3fc5
4 touches
1 conflict
0x8cf3d245…1d0d
0x34ae4d…3fc5
4 touches
1 conflict
0xa987699f…eabe
0x34ae4d…3fc5
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity