← previous blocknext block →recent activity
Analyzing
Block #100,246,856
13 transactions · 12 stateful · 2026-08-29 17:43:50 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,246,856 · 13 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
5w09w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdaf5ed0d…16ae
0x34b655…2a6f
4 touches
1 conflict
0xdaf5ed0d…16af
0x34b655…2a6f
4 touches
1 conflict
0xe5108b69…f783
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7da56943…9753
0x34b655…2a6f
4 touches
1 conflict
0x8b7e1779…0404
0x34b655…2a6f
3 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
1 conflict on slot 0xdaf5ed0d35…7116ae
Audit this contract →
← previous block·next block →recent activity