← previous blocknext block →recent activity
Analyzing
Block #100,850,389
38 transactions · 32 stateful · 2026-08-31 20:23:39 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,850,389 · 38 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
1w02w15w06w17w211w012w120w022w223w126w131w034w336w437w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x124ca49c…30c8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb4c703ab…f8cf
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x354e383e…817c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
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
3 conflicts on slot 0x124ca49c22…f030c8
Audit this contract →
← previous block·next block →recent activity