← previous blocknext block →recent activity
Analyzing
Block #99,457,954
34 transactions · 26 stateful · 2026-08-26 23:18:01 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,457,954 · 34 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
2w03w14w05w29w010w111w213w114w015w019w221w225w128w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6206c6d…705a
0x065c9d…c394
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x8a2f9a36…fb4a
0x2d82ac…5fd8
4 touches
1 conflict
0x7e5ea60a…c4aa
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
3 conflicts on slot 0xc6206c6d36…56705a
Audit this contract →
← previous block·next block →recent activity