← previous blocknext block →recent activity
Analyzing
Block #100,752,633
25 transactions · 23 stateful · 2026-08-31 12:11:28 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,752,633 · 25 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
1w02w13w08w010w113w014w115w216w317w420w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24d8f4db…4703
0x851145…3f07
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb2
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x851145ea…9f3f07
10 conflicts on slot 0x24d8f4db6d…454703
Audit this contract →
← previous block·next block →recent activity