← previous blocknext block →recent activity
Analyzing
Block #101,303,498
13 transactions · 11 stateful · 2026-09-02 10:23:27 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,303,498 · 13 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
1w02w18w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28eed2ad…c4b2
0x34b655…2a6f
4 touches
1 conflict
0xf3bc99c2…069f
0x34b655…2a6f
4 touches
1 conflict
0xdf7d369d…b2c5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb5f5f775…010b
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
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 0x28eed2ad33…59c4b2
Audit this contract →
← previous block·next block →recent activity