← previous blocknext block →recent activity
Analyzing
Block #108,630,219
29 transactions · 26 stateful · 2026-09-28 02:19:02 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,630,219 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w38w417w518w525w426w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x899ed66a…b2e0
0x065c9d…c394
5 touches
3 conflicts
0xb86571c5…9927
0x851145…3f07
4 touches
1 conflict
0xb98b49be…53f9
0x851145…3f07
4 touches
1 conflict
0xc892ba62…7015
0x851145…3f07
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
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
15 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity