← previous blocknext block →recent activity
Analyzing
Block #100,735,403
8 transactions · 8 stateful · 2026-08-31 10:44:48 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,735,403 · 8 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
1w02w13w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x474e5df9…821f
0x851145…3f07
4 touches
1 conflict
0x5f0a01c3…8269
0x851145…3f07
4 touches
1 conflict
0x87d39100…7270
0x851145…3f07
4 touches
1 conflict
0xd08c7140…f070
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity