← previous blocknext block →recent activity
Analyzing
Block #108,672,283
25 transactions · 21 stateful · 2026-09-28 05:50:54 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,672,283 · 25 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
1w02w05w06w17w111w212w113w215w317w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5ba4f1a…6ce3
0x065c9d…c394
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xc3e72796…a3ca
0x34b655…2a6f
6 touches
3 conflicts
0x732d4b2d…2590
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
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: Market-MON/USDC
6 conflicts on slot 0xc5ba4f1a90…006ce3
Audit this contract →
← previous block·next block →recent activity