← previous blocknext block →recent activity
Analyzing
Block #100,135,962
11 transactions · 11 stateful · 2026-08-29 08:24:56 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,135,962 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x13aae63e…db6b
0x065c9d…c394
2 touches
0 conflicts
0x7604fb52…6484
0x065c9d…c394
2 touches
0 conflicts
0x950076ab…7125
0x065c9d…c394
2 touches
0 conflicts
0xd8bfa141…3571
0x065c9d…c394
2 touches
0 conflicts
0xf025e8f1…851b
0x065c9d…c394
2 touches
0 conflicts
0xf1e0de1b…215a
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity