← previous blocknext block →recent activity
Analyzing
Block #101,502,169
12 transactions · 11 stateful · 2026-09-03 03:03:10 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,502,169 · 12 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
1w02w07w18w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5eb20016…eb59
0x34b655…2a6f
4 touches
1 conflict
0x2d4cd1ab…19b0
0x34b655…2a6f
4 touches
1 conflict
0xc5d1a242…8f27
0xd32edf…ff58
3 touches
1 conflict
0x17196303…ebe3
0x34b655…2a6f
2 touches
0 conflicts
0x2f835a56…0ded
0x34b655…2a6f
2 touches
0 conflicts
0x43b34fb2…7b88
0x34b655…2a6f
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 0x2029b74ed0…e1c206
Audit this contract →
← previous block·next block →recent activity