← previous blocknext block →recent activity
Analyzing
Block #100,786,224
25 transactions · 22 stateful · 2026-08-31 15:00:37 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,786,224 · 25 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
1w02w14w05w06w17w08w19w112w013w116w119w220w222w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x39773cec…38ed
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x55cde02d…89cb
0x34b655…2a6f
4 touches
1 conflict
0x8a7af3fd…72a6
0x34b655…2a6f
4 touches
1 conflict
0x98b14f9b…08b3
0x34b655…2a6f
4 touches
1 conflict
0xa020506f…7c60
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity