← previous blocknext block →recent activity
Analyzing
Block #101,968,233
15 transactions · 13 stateful · 2026-09-04 18:10:49 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,968,233 · 15 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
3w04w18w09w110w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8f860c0…35c9
0x34b655…2a6f
4 touches
1 conflict
0x9feec606…4ad5
0x34b655…2a6f
4 touches
1 conflict
0xb40e601f…bf98
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xb826ef15…d248
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x04d4f30d…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
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 0xe8f860c039…3435c9
Audit this contract →
← previous block·next block →recent activity