← previous blocknext block →recent activity
Analyzing
Block #100,123,629
16 transactions · 13 stateful · 2026-08-29 07:22:47 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,123,629 · 16 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
4w09w111w012w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cccbb7…130e
0x8964d7…10f8
4 touches
1 conflict
0x46cccbb7…1308
0x8964d7…10f8
4 touches
1 conflict
0x46cccbb7…130b
0x8964d7…10f8
4 touches
1 conflict
0x46cccbb7…130c
0x8964d7…10f8
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd8ca0135…c1c3
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 0x46cccbb71e…e3130e
Audit this contract →
← previous block·next block →recent activity