← previous blocknext block →recent activity
Analyzing
Block #100,610,652
21 transactions · 19 stateful · 2026-08-31 00:17:17 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,610,652 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w06w17w28w39w410w511w012w114w115w216w117w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x5f430f62…c362
0x34b655…2a6f
4 touches
1 conflict
0x68e09043…7821
0x34b655…2a6f
4 touches
1 conflict
0xafb519c4…cba0
0x34b655…2a6f
4 touches
1 conflict
0xb7ce83b1…2c96
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe2de1aea…8024
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity