← previous blocknext block →recent activity
Analyzing
Block #101,985,287
24 transactions · 21 stateful · 2026-09-04 19:37:16 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,985,287 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w011w112w214w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x256918f1…c4d0
0x34b655…2a6f
10 touches
10 conflicts
0x6c02fb45…7ae9
0x99c7a7…8bf0
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x06a8b17c…46e5
0x754704…b603
4 touches
1 conflict
0x420c4a20…aa5f
0x754704…b603
4 touches
1 conflict
0x7805c8f7…1376
0x754704…b603
4 touches
1 conflict
0x461e2f32…8325
0x99c7a7…8bf0
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
10 conflicts on slot 0x256918f186…59c4d0
Audit this contract →
← previous block·next block →recent activity