← previous blocknext block →recent activity
Analyzing
Block #101,306,873
16 transactions · 16 stateful · 2026-09-02 10:40:27 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,306,873 · 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
9w010w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe708c9f4…b505
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xdba775cd…7b75
0x34b655…2a6f
4 touches
1 conflict
0x27fcff4c…e81e
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5c43fdb2…08b7
0x34b655…2a6f
4 touches
1 conflict
0x5ddc4a77…765e
0x34b655…2a6f
4 touches
1 conflict
0x6c28863e…840e
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 0xe708c9f498…68b505
Audit this contract →
← previous block·next block →recent activity