← previous blocknext block →recent activity
Analyzing
Block #101,249,143
12 transactions · 12 stateful · 2026-09-02 05:49:58 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,249,143 · 12 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb77dc863…dd3d
0x34b655…2a6f
4 touches
1 conflict
0x24bb46f7…3853
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x7aa91b8f…d070
0x34ae4d…3fc5
2 touches
0 conflicts
0xb05cd4f5…73d0
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6a9e
0x34ae4d…3fc5
2 touches
0 conflicts
0xe2263bea…6aa2
0x34ae4d…3fc5
2 touches
0 conflicts
0xf1a14809…56fd
0x34ae4d…3fc5
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 0xb77dc86363…59dd3d
Audit this contract →
← previous block·next block →recent activity