← previous blocknext block →recent activity
Analyzing
Block #101,937,735
17 transactions · 16 stateful · 2026-09-04 15:36:09 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,937,735 · 17 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
2w03w14w25w19w010w111w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf139b130…d132
0x34b655…2a6f
6 touches
3 conflicts
0x3167d7d8…a06b
0x34b655…2a6f
6 touches
3 conflicts
0xac27d4e9…fffc
0x34b655…2a6f
6 touches
3 conflicts
0xadc848ee…5cb2
0x34b655…2a6f
6 touches
3 conflicts
0x56e0d685…c960
0x34b655…2a6f
4 touches
1 conflict
0x7fd951f1…fe49
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8ea854f7…7094
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
3 conflicts on slot 0xf139b130f5…fdd132
Audit this contract →
← previous block·next block →recent activity