← previous blocknext block →recent activity
Analyzing
Block #101,669,102
13 transactions · 12 stateful · 2026-09-03 17:02:56 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,669,102 · 13 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
1w03w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05e25943…dd95
0x34b655…2a6f
4 touches
1 conflict
0x5a22f456…b743
0x34b655…2a6f
4 touches
1 conflict
0xb6edb3e8…48be
0x34b655…2a6f
4 touches
1 conflict
0xcb9d7e0c…c3c4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13ad89b9…c800
0x34b655…2a6f
2 touches
0 conflicts
0x17b7d0d0…1166
0x34b655…2a6f
2 touches
0 conflicts
0x1ddae525…7f4f
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 0x05e25943fe…f2dd95
Audit this contract →
← previous block·next block →recent activity