← previous blocknext block →recent activity
Analyzing
Block #100,919,506
26 transactions · 17 stateful · 2026-09-01 02:11:18 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,919,506 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w08w019w120w121w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1dedc384…ff57
0x851145…3f07
4 touches
1 conflict
0x474e5df9…821f
0x851145…3f07
4 touches
1 conflict
0x87d39100…7270
0x851145…3f07
4 touches
1 conflict
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0x7c9f1949…a444
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity