← previous blocknext block →recent activity
Analyzing
Block #100,920,841
22 transactions · 21 stateful · 2026-09-01 02:18:01 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,920,841 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w28w010w111w212w117w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69f0d775…13f5
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa2f03f1f…5003
0xa6afd3…d132
4 touches
1 conflict
0x0e8e1870…8c31
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
1 conflict on slot 0x69f0d775d8…1b13f5
Audit this contract →
← previous block·next block →recent activity