← previous blocknext block →recent activity
Analyzing
Block #100,876,231
33 transactions · 26 stateful · 2026-08-31 22:33:38 UTC
Parallelism
88/100
Blocked
46%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,876,231 · 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
3w04w05w18w110w212w013w014w115w223w224w325w026w227w129w130w332w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74e485b1…d380
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x0555322a…5cfc
0x34b655…2a6f
4 touches
1 conflict
0x0cad650f…0ff3
0x34b655…2a6f
4 touches
1 conflict
0x1546d8ad…f17f
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
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 0x74e485b13a…f0d380
Audit this contract →
← previous block·next block →recent activity