← previous blocknext block →recent activity
Analyzing
Block #101,800,920
9 transactions · 9 stateful · 2026-09-04 04:05:57 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,800,920 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05e1eba1…6491
0x34b655…2a6f
4 touches
1 conflict
0x733c7779…a647
0x34b655…2a6f
4 touches
1 conflict
0xbeedaa05…9eda
0x34b655…2a6f
4 touches
1 conflict
0xc09c3422…3c8b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeff3e2cb…4bc0
0x34b655…2a6f
4 touches
1 conflict
0x809f2ba8…89d3
0x34b655…2a6f
4 touches
1 conflict
0x5b0227d5…1940
0x34b655…2a6f
2 touches
0 conflicts
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 0x05e1eba1fd…456491
Audit this contract →
← previous block·next block →recent activity