← previous blocknext block →recent activity
Analyzing
Block #100,159,960
14 transactions · 14 stateful · 2026-08-29 10:25:49 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,159,960 · 14 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
1w02w14w06w07w18w19w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19df614c…3b04
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x19df614c…3aff
0x8964d7…10f8
6 touches
3 conflicts
0x19df614c…3b00
0x8964d7…10f8
6 touches
3 conflicts
0x19df614c…3b03
0x8964d7…10f8
6 touches
3 conflicts
0xca5b9231…3bd1
0x34b655…2a6f
4 touches
1 conflict
0xccaf5fb4…fb1a
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x19df614c3b…1c3b04
Audit this contract →
← previous block·next block →recent activity