← previous blocknext block →recent activity
Analyzing
Block #101,674,708
19 transactions · 17 stateful · 2026-09-03 17:31:09 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,674,708 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w312w115w417w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0x7744726e…1419
0x34b655…2a6f
6 touches
3 conflicts
0x46182d27…421e
0x34b655…2a6f
4 touches
1 conflict
0x53043411…237a
0x34b655…2a6f
4 touches
1 conflict
0x70d81211…f49f
0x34b655…2a6f
4 touches
1 conflict
0x7577950f…0a2d
0x34b655…2a6f
4 touches
1 conflict
0x885efce3…7496
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity