← previous blocknext block →recent activity
Analyzing
Block #101,818,022
12 transactions · 11 stateful · 2026-09-04 05:31:58 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,818,022 · 12 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
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x87c3dfca…7ce9
0x754704…b603
4 touches
1 conflict
0xbb95fb3e…c47b
0x754704…b603
4 touches
1 conflict
0x27c8497b…dcc4
0x754704…b603
4 touches
1 conflict
0x5f28dff7…3ddd
0x99c7a7…8bf0
4 touches
1 conflict
0x990848fb…bf35
0x99c7a7…8bf0
4 touches
1 conflict
0x042c5324…2d20
0x8f415d…5241
3 touches
1 conflict
0x9b36f19f…fa5a
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity