← previous blocknext block →recent activity
Analyzing
Block #101,816,304
24 transactions · 21 stateful · 2026-09-04 05:23:20 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,816,304 · 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
1w03w14w05w16w27w39w010w113w014w115w116w220w021w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd98afa6e…3364
0x34b655…2a6f
6 touches
3 conflicts
0xe6875750…9542
0x34b655…2a6f
6 touches
3 conflicts
0x7daf6443…fd36
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x987859be…2686
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity