← previous blocknext block →recent activity
Analyzing
Block #108,548,952
18 transactions · 17 stateful · 2026-09-27 19:29:43 UTC
Parallelism
83/100
Blocked
12%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,548,952 · 18 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
6w07w113w014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x36b63189…f531
0x065c9d…c394
3 touches
1 conflict
0x6076d626…e6a3
0x065c9d…c394
3 touches
1 conflict
0xc4c4bfb1…a014
0x065c9d…c394
3 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x6293016e…b6a7
0x34b655…2a6f
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity