← previous blocknext block →recent activity
Analyzing
Block #100,921,580
21 transactions · 18 stateful · 2026-09-01 02:21:44 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,921,580 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w18w09w110w111w212w313w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96a207cf…cda5
0x34b655…2a6f
8 touches
6 conflicts
0x0e1d3af4…1b95
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x6b0e4b70…48a5
0x34b655…2a6f
4 touches
1 conflict
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0x831f75b4…945d
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
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
6 conflicts on slot 0x96a207cf52…e9cda5
Audit this contract →
← previous block·next block →recent activity