← previous blocknext block →recent activity
Analyzing
Block #100,119,285
24 transactions · 21 stateful · 2026-08-29 07:00:54 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,119,285 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w213w117w118w220w321w222w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedee7e09…6888
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xd08d1657…e444
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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 0xedee7e090f…056888
Audit this contract →
← previous block·next block →recent activity