← previous blocknext block →recent activity
Analyzing
Block #100,791,342
23 transactions · 21 stateful · 2026-08-31 15:26:23 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,791,342 · 23 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
1w02w03w16w07w114w115w016w018w119w121w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb1d1974…2679
0x8964d7…10f8
4 touches
1 conflict
0xeb1d1974…2675
0x8964d7…10f8
4 touches
1 conflict
0xeb1d1974…2678
0x8964d7…10f8
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2f74f175…9289
0x34ae4d…3fc5
4 touches
1 conflict
0xdde1e1b8…a9da
0x34ae4d…3fc5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xeb1d19742b…9d2679
Audit this contract →
← previous block·next block →recent activity