← previous blocknext block →recent activity
Analyzing
Block #100,139,071
10 transactions · 10 stateful · 2026-08-29 08:40:39 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,139,071 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d3c809f…594d
0x8964d7…10f8
4 touches
1 conflict
0x6d3c809f…594e
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x6d3c809f…5949
0x8964d7…10f8
4 touches
1 conflict
0x6d3c809f…594a
0x8964d7…10f8
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
2 touches
0 conflicts
0x177211e2…1c2d
0x754704…b603
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x6d3c809fe1…69594d
Audit this contract →
← previous block·next block →recent activity