← previous blocknext block →recent activity
Analyzing
Block #100,619,789
13 transactions · 11 stateful · 2026-08-31 01:03:14 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,619,789 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w09w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bf496e1…aae0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x726ef79c…03bf
0x851145…3f07
4 touches
1 conflict
0xf52df78b…16a0
0x851145…3f07
4 touches
1 conflict
0x8f4e041c…01ae
0x34b655…2a6f
2 touches
0 conflicts
0xa7f7a563…4504
0x34b655…2a6f
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 0x2bf496e1e7…aeaae0
Audit this contract →
← previous block·next block →recent activity