← previous blocknext block →recent activity
Analyzing
Block #100,602,594
30 transactions · 24 stateful · 2026-08-30 23:36:44 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,602,594 · 30 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
2w03w17w08w014w215w318w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0x24bb46f7…3853
0x34b655…2a6f
4 touches
1 conflict
0xef49234d…3e26
0x40c49f…2af0
3 touches
1 conflict
0xdb24e5c2…3532
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: 0xf5b5f7f8…a36d70
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity