← previous blocknext block →recent activity
Analyzing
Block #101,094,501
21 transactions · 16 stateful · 2026-09-01 16:52:02 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,094,501 · 21 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
1w03w14w25w37w09w114w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xed5e5f75…05b2
0x065c9d…c394
3 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x3e1e8e54…9c83
0x2a68ba…90c5
2 touches
0 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity