← previous blocknext block →recent activity
Analyzing
Block #100,919,804
26 transactions · 22 stateful · 2026-09-01 02:12:48 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,919,804 · 26 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
2w03w14w25w06w19w015w016w117w018w120w021w123w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x34b0072d…0ef3
0x40c49f…2af0
4 touches
1 conflict
0x84675013…74c6
0x40c49f…2af0
4 touches
1 conflict
0x0e8e1870…8c31
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x2827ae77…4368
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity