← previous blocknext block →recent activity
Analyzing
Block #100,583,341
15 transactions · 14 stateful · 2026-08-30 21:59:53 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,583,341 · 15 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
4w05w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9c91db3…8ac8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1fb8364c…c10d
0x34b655…2a6f
2 touches
0 conflicts
0x38a429dd…bcb0
0x34b655…2a6f
2 touches
0 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
2 touches
0 conflicts
0x52404f3d…4c2e
0x34b655…2a6f
2 touches
0 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
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 0xd9c91db375…1a8ac8
Audit this contract →
← previous block·next block →recent activity