← previous blocknext block →recent activity
Analyzing
Block #101,895,384
14 transactions · 12 stateful · 2026-09-04 12:01:20 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,895,384 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38f283d2…339a
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0xb654bd89…a83b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5c7b5ec0…0764
0x34b655…2a6f
2 touches
0 conflicts
0x67043b0b…97d7
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 0x38f283d252…df339a
Audit this contract →
← previous block·next block →recent activity