← previous blocknext block →recent activity
Analyzing
Block #102,739,137
20 transactions · 19 stateful · 2026-09-07 11:13:43 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,739,137 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w17w18w29w011w312w414w115w018w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x74e485b1…d380
0x34b655…2a6f
6 touches
3 conflicts
0x48ed1159…abe9
0x34ae4d…3fc5
6 touches
3 conflicts
0xd9446f57…fc1e
0x065c9d…c394
5 touches
3 conflicts
0x882a3d91…688e
0x065c9d…c394
4 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity