← previous blocknext block →recent activity
Analyzing
Block #100,160,897
10 transactions · 10 stateful · 2026-08-29 10:30:32 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,160,897 · 10 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
6w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52828921…3699
0x8964d7…10f8
4 touches
1 conflict
0x36979487…c451
0x8964d7…10f8
4 touches
1 conflict
0x36979487…c452
0x8964d7…10f8
4 touches
1 conflict
0x36979487…c454
0x8964d7…10f8
4 touches
1 conflict
0x52828921…3696
0x8964d7…10f8
4 touches
1 conflict
0x52828921…3697
0x8964d7…10f8
4 touches
1 conflict
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0x72ce1ab9…d304
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 0x528289215b…fe3699
Audit this contract →
← previous block·next block →recent activity