← previous blocknext block →recent activity
Analyzing
Block #101,095,073
17 transactions · 17 stateful · 2026-09-01 16:54:55 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,095,073 · 17 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
1w03w04w05w16w112w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xeaced15b…2221
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc4e19ae4…0788
0xe7cd86…c82d
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
2 touches
0 conflicts
0x3602eb96…2683
0x34b655…2a6f
2 touches
0 conflicts
0x46d5925f…afff
0x34b655…2a6f
2 touches
0 conflicts
0x6b267bdf…b173
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: 0x40c49f17…d22af0
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity