← previous blocknext block →recent activity
Analyzing
Block #94,851,714
30 transactions · 19 stateful · 2026-08-10 18:53:10 UTC
Parallelism
87/100
Blocked
58%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,851,714 · 30 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
1w02w03w14w06w18w212w213w317w220w021w123w326w228w129w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0x1baca9c3…2b23
0x34b655…2a6f
4 touches
1 conflict
0x3fc40870…7ef4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xea02471d…1542
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 0xb33ff82315…a81188
Audit this contract →
← previous block·next block →recent activity