← previous blocknext block →recent activity
Analyzing
Block #100,893,453
23 transactions · 23 stateful · 2026-09-01 00:00:16 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,893,453 · 23 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
1w02w03w14w15w06w17w09w111w114w215w218w019w221w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x38963aeb…c33f
0xa6afd3…d132
4 touches
1 conflict
0x39773cec…38ed
0xa6afd3…d132
4 touches
1 conflict
0xd1c12107…a0cb
0xa6afd3…d132
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity