← previous blocknext block →recent activity
Analyzing
Block #101,985,726
25 transactions · 25 stateful · 2026-09-04 19:39:31 UTC
Parallelism
88/100
Blocked
16%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,985,726 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w014w020w121w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x556beb43…e627
0x34b655…2a6f
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
4 touches
1 conflict
0xb652da8f…1216
0x754704…b603
4 touches
1 conflict
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0x14636d9e…78ad
0x99c7a7…8bf0
4 touches
1 conflict
0x2a46edb5…b5bd
0x99c7a7…8bf0
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x556beb4322…c0e627
Audit this contract →
← previous block·next block →recent activity