← previous blocknext block →recent activity
Analyzing
Block #100,784,792
20 transactions · 19 stateful · 2026-08-31 14:53:24 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,784,792 · 20 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
2w04w15w06w17w08w19w010w111w012w114w215w217w018w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2dfd9bc…3eec
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
4 touches
1 conflict
0x7aa91b8f…d070
0x34ae4d…3fc5
4 touches
1 conflict
0xb05cd4f5…73d0
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6a9d
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6aa2
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 0xd2dfd9bc48…fc3eec
Audit this contract →
← previous block·next block →recent activity