← previous blocknext block →recent activity
Analyzing
Block #100,085,524
18 transactions · 18 stateful · 2026-08-29 04:10:54 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,085,524 · 18 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
1w02w03w16w012w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50c61506…343f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x02f4f6e2…47c6
0x754704…b603
4 touches
1 conflict
0x0449d018…e334
0x754704…b603
4 touches
1 conflict
0xe332b0a5…0bdb
0x754704…b603
4 touches
1 conflict
0x3b41d761…cd85
0x99c7a7…8bf0
4 touches
1 conflict
0xe10ff4f0…94b7
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…002c
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: Perpl
1 conflict on slot 0x50c615063f…63343f
Audit this contract →
← previous block·next block →recent activity