← previous blocknext block →recent activity
Analyzing
Block #100,095,709
17 transactions · 15 stateful · 2026-08-29 05:02:11 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,095,709 · 17 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
3w04w05w16w09w110w111w212w213w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91cdfdeb…7feb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x7de62625…96b8
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x91cdfdebc5…487feb
Audit this contract →
← previous block·next block →recent activity