← previous blocknext block →recent activity
Analyzing
Block #100,878,849
36 transactions · 24 stateful · 2026-08-31 22:46:48 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,878,849 · 36 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w19w016w017w220w326w227w430w031w132w134w135w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf984d8ab…6e4f
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x26253352…1a75
0x34b655…2a6f
4 touches
1 conflict
0x48719cbe…5484
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0xf984d8ab41…c96e4f
Audit this contract →
← previous block·next block →recent activity