← previous blocknext block →recent activity
Analyzing
Block #101,680,527
19 transactions · 18 stateful · 2026-09-03 18:00:25 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,680,527 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w17w08w110w011w312w016w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e0f1bec…86e0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x29cac3f0…d958
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4babcbd0…e24c
0x34b655…2a6f
4 touches
1 conflict
0x51af0e92…4020
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x9e0f1bec14…aa86e0
Audit this contract →
← previous block·next block →recent activity