← previous blocknext block →recent activity
Analyzing
Block #100,626,625
17 transactions · 17 stateful · 2026-08-31 01:37:38 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,626,625 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w19w010w111w112w013w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe73a5eb9…5d49
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x9b248417…ac5e
0x40c49f…2af0
4 touches
1 conflict
0xdce17450…7f32
0x40c49f…2af0
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
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 0xe73a5eb9f5…fd5d49
Audit this contract →
← previous block·next block →recent activity