← previous blocknext block →recent activity
Analyzing
Block #101,674,831
19 transactions · 18 stateful · 2026-09-03 17:31:46 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,674,831 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w27w38w413w114w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xf1eadfaf…34e5
0x34b655…2a6f
4 touches
1 conflict
0x2ac7f66e…e903
0x34b655…2a6f
4 touches
1 conflict
0x3d538e8e…702c
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0x51af0e92…4020
0x34b655…2a6f
4 touches
1 conflict
0x62efa201…0a74
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity