← previous blocknext block →recent activity
Analyzing
Block #101,970,275
16 transactions · 15 stateful · 2026-09-04 18:21:08 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,970,275 · 16 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
1w02w03w14w05w16w211w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x09a70817…c3bf
0x34b655…2a6f
2 touches
0 conflicts
0x126036d8…3b50
0x34b655…2a6f
2 touches
0 conflicts
0x25fd5528…ff50
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 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity